A Count problem has been changed based upon stat decision - Need helpA Count problem has been changed based upon stat decision - Need help (38 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A Count problem has been changed based upon stat decision - Need help (44 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A Count problem has been changed based upon stat decision - Need help (83 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: A Count problem has been changed based upon stat decision - Need help (137 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: A Count problem has been changed based upon stat decision - Need help (133 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: A Count problem has been changed based upon stat decision - Need help (176 lines) From: toby dunn <tobydunn@HOTMAIL.COM> A Count questionA Count question (29 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A Count question (74 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: A Count question (87 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A Count question (93 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A Count question (75 lines) From: Robin R High <rhigh@UNMC.EDU> Re: A Count question (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: A Count question (63 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A Count question (69 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A Count question (87 lines) From: Guido T <cymraegerict@GMAIL.COM> Re: A Count question (128 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: A Count question (221 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> A Data manupulation questionA Data manupulation question (36 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A Data manupulation question (65 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: A Data manupulation question (72 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: A Data manupulation question (82 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: A Data manupulation question (100 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A Data manupulation question (105 lines) From: Guido T <cymraegerict@GMAIL.COM> Re: A Data manupulation question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> A Format quesion - UrgentRe: A Format quesion - Urgent (75 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A Format quesion - Urgent (89 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: A Format quesion - Urgent (94 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: A Format quesion - Urgent (128 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: A Format quesion - Urgent (161 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: A Format quesion - Urgent (170 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: A Format quesion - Urgent (145 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> A better way?A better way? (57 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: A better way? (86 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: A better way? (108 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> A data manupulation QuestionA data manupulation Question (32 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (41 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (81 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (80 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (81 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (25 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (31 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (38 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (48 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: A data manupulation Question (60 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Automatic reply: A Count problem has been changed based upon stat decision - Need helpAutomatic reply: A Count problem has been changed based upon stat decision - Need help (20 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607)Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607) (13 lines) From: Erika Steinmetz <esteinmetz@AAMC.ORG> Automatic reply: creating new variables from variable names stored in another variableAutomatic reply: creating new variables from variable names stored in another variable (12 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Batch SAS when both 9.1 and 9.2 existBatch SAS when both 9.1 and 9.2 exist (35 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Batch SAS when both 9.1 and 9.2 exist (55 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Batch SAS when both 9.1 and 9.2 exist (77 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Batch SAS when both 9.1 and 9.2 exist (46 lines) From: Andrew Hansen <hansen.andrew.e@GMAIL.COM> Re: Batch SAS when both 9.1 and 9.2 exist (15 lines) From: Lorne Klassen <lk1@ROGERS.COM> Clinical SAS Programmer for MAClinical SAS Programmer for MA (60 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> DATALINES within a macro?DATALINES within a macro? (22 lines) From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA> Re: DATALINES within a macro? (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: DATALINES within a macro? (57 lines) From: Charlie Huang <charlie.chao.huang@GMAIL.COM> Re: DATALINES within a macro? (83 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (41 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: DATALINES within a macro? (44 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: DATALINES within a macro? (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: DATALINES within a macro? (69 lines) From: Arthur Tabachneck <art297@ROGERS.COM> DF in mixed models with repeated measuresDF in mixed models with repeated measures (65 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: DF in mixed models with repeated measures (110 lines) From: Robin R High <rhigh@UNMC.EDU> Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
A Count questionA Count question (29 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A Count question (74 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: A Count question (87 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A Count question (93 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A Count question (75 lines) From: Robin R High <rhigh@UNMC.EDU> Re: A Count question (118 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: A Count question (63 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A Count question (69 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A Count question (87 lines) From: Guido T <cymraegerict@GMAIL.COM> Re: A Count question (128 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: A Count question (221 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> A Data manupulation questionA Data manupulation question (36 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A Data manupulation question (65 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: A Data manupulation question (72 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: A Data manupulation question (82 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: A Data manupulation question (100 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A Data manupulation question (105 lines) From: Guido T <cymraegerict@GMAIL.COM> Re: A Data manupulation question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> A Format quesion - UrgentRe: A Format quesion - Urgent (75 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A Format quesion - Urgent (89 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: A Format quesion - Urgent (94 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: A Format quesion - Urgent (128 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: A Format quesion - Urgent (161 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: A Format quesion - Urgent (170 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: A Format quesion - Urgent (145 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> A better way?A better way? (57 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: A better way? (86 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: A better way? (108 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> A data manupulation QuestionA data manupulation Question (32 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (41 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (81 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (80 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (81 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (25 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (31 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (38 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (48 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: A data manupulation Question (60 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Automatic reply: A Count problem has been changed based upon stat decision - Need helpAutomatic reply: A Count problem has been changed based upon stat decision - Need help (20 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607)Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607) (13 lines) From: Erika Steinmetz <esteinmetz@AAMC.ORG> Automatic reply: creating new variables from variable names stored in another variableAutomatic reply: creating new variables from variable names stored in another variable (12 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Batch SAS when both 9.1 and 9.2 existBatch SAS when both 9.1 and 9.2 exist (35 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Batch SAS when both 9.1 and 9.2 exist (55 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Batch SAS when both 9.1 and 9.2 exist (77 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Batch SAS when both 9.1 and 9.2 exist (46 lines) From: Andrew Hansen <hansen.andrew.e@GMAIL.COM> Re: Batch SAS when both 9.1 and 9.2 exist (15 lines) From: Lorne Klassen <lk1@ROGERS.COM> Clinical SAS Programmer for MAClinical SAS Programmer for MA (60 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> DATALINES within a macro?DATALINES within a macro? (22 lines) From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA> Re: DATALINES within a macro? (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: DATALINES within a macro? (57 lines) From: Charlie Huang <charlie.chao.huang@GMAIL.COM> Re: DATALINES within a macro? (83 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (41 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: DATALINES within a macro? (44 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: DATALINES within a macro? (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: DATALINES within a macro? (69 lines) From: Arthur Tabachneck <art297@ROGERS.COM> DF in mixed models with repeated measuresDF in mixed models with repeated measures (65 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: DF in mixed models with repeated measures (110 lines) From: Robin R High <rhigh@UNMC.EDU> Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
A Data manupulation questionA Data manupulation question (36 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A Data manupulation question (65 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: A Data manupulation question (72 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: A Data manupulation question (82 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: A Data manupulation question (100 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A Data manupulation question (105 lines) From: Guido T <cymraegerict@GMAIL.COM> Re: A Data manupulation question (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> A Format quesion - UrgentRe: A Format quesion - Urgent (75 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A Format quesion - Urgent (89 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: A Format quesion - Urgent (94 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: A Format quesion - Urgent (128 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: A Format quesion - Urgent (161 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: A Format quesion - Urgent (170 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: A Format quesion - Urgent (145 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> A better way?A better way? (57 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: A better way? (86 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: A better way? (108 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> A data manupulation QuestionA data manupulation Question (32 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (41 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (81 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (80 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (81 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (25 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (31 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (38 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (48 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: A data manupulation Question (60 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Automatic reply: A Count problem has been changed based upon stat decision - Need helpAutomatic reply: A Count problem has been changed based upon stat decision - Need help (20 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607)Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607) (13 lines) From: Erika Steinmetz <esteinmetz@AAMC.ORG> Automatic reply: creating new variables from variable names stored in another variableAutomatic reply: creating new variables from variable names stored in another variable (12 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Batch SAS when both 9.1 and 9.2 existBatch SAS when both 9.1 and 9.2 exist (35 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Batch SAS when both 9.1 and 9.2 exist (55 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Batch SAS when both 9.1 and 9.2 exist (77 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Batch SAS when both 9.1 and 9.2 exist (46 lines) From: Andrew Hansen <hansen.andrew.e@GMAIL.COM> Re: Batch SAS when both 9.1 and 9.2 exist (15 lines) From: Lorne Klassen <lk1@ROGERS.COM> Clinical SAS Programmer for MAClinical SAS Programmer for MA (60 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> DATALINES within a macro?DATALINES within a macro? (22 lines) From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA> Re: DATALINES within a macro? (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: DATALINES within a macro? (57 lines) From: Charlie Huang <charlie.chao.huang@GMAIL.COM> Re: DATALINES within a macro? (83 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (41 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: DATALINES within a macro? (44 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: DATALINES within a macro? (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: DATALINES within a macro? (69 lines) From: Arthur Tabachneck <art297@ROGERS.COM> DF in mixed models with repeated measuresDF in mixed models with repeated measures (65 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: DF in mixed models with repeated measures (110 lines) From: Robin R High <rhigh@UNMC.EDU> Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
A Format quesion - UrgentRe: A Format quesion - Urgent (75 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A Format quesion - Urgent (89 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: A Format quesion - Urgent (94 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: A Format quesion - Urgent (128 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: A Format quesion - Urgent (161 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: A Format quesion - Urgent (170 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: A Format quesion - Urgent (145 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> A better way?A better way? (57 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: A better way? (86 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: A better way? (108 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> A data manupulation QuestionA data manupulation Question (32 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (41 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (81 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (80 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (81 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (25 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (31 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (38 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (48 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: A data manupulation Question (60 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Automatic reply: A Count problem has been changed based upon stat decision - Need helpAutomatic reply: A Count problem has been changed based upon stat decision - Need help (20 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607)Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607) (13 lines) From: Erika Steinmetz <esteinmetz@AAMC.ORG> Automatic reply: creating new variables from variable names stored in another variableAutomatic reply: creating new variables from variable names stored in another variable (12 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Batch SAS when both 9.1 and 9.2 existBatch SAS when both 9.1 and 9.2 exist (35 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Batch SAS when both 9.1 and 9.2 exist (55 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Batch SAS when both 9.1 and 9.2 exist (77 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Batch SAS when both 9.1 and 9.2 exist (46 lines) From: Andrew Hansen <hansen.andrew.e@GMAIL.COM> Re: Batch SAS when both 9.1 and 9.2 exist (15 lines) From: Lorne Klassen <lk1@ROGERS.COM> Clinical SAS Programmer for MAClinical SAS Programmer for MA (60 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> DATALINES within a macro?DATALINES within a macro? (22 lines) From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA> Re: DATALINES within a macro? (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: DATALINES within a macro? (57 lines) From: Charlie Huang <charlie.chao.huang@GMAIL.COM> Re: DATALINES within a macro? (83 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (41 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: DATALINES within a macro? (44 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: DATALINES within a macro? (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: DATALINES within a macro? (69 lines) From: Arthur Tabachneck <art297@ROGERS.COM> DF in mixed models with repeated measuresDF in mixed models with repeated measures (65 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: DF in mixed models with repeated measures (110 lines) From: Robin R High <rhigh@UNMC.EDU> Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
A better way?A better way? (57 lines) From: Valerie Hastings <valerie.hastings@STATCAN.GC.CA> Re: A better way? (86 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: A better way? (108 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> A data manupulation QuestionA data manupulation Question (32 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (41 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (81 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (80 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (81 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (25 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (31 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (38 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (48 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: A data manupulation Question (60 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Automatic reply: A Count problem has been changed based upon stat decision - Need helpAutomatic reply: A Count problem has been changed based upon stat decision - Need help (20 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607)Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607) (13 lines) From: Erika Steinmetz <esteinmetz@AAMC.ORG> Automatic reply: creating new variables from variable names stored in another variableAutomatic reply: creating new variables from variable names stored in another variable (12 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Batch SAS when both 9.1 and 9.2 existBatch SAS when both 9.1 and 9.2 exist (35 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Batch SAS when both 9.1 and 9.2 exist (55 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Batch SAS when both 9.1 and 9.2 exist (77 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Batch SAS when both 9.1 and 9.2 exist (46 lines) From: Andrew Hansen <hansen.andrew.e@GMAIL.COM> Re: Batch SAS when both 9.1 and 9.2 exist (15 lines) From: Lorne Klassen <lk1@ROGERS.COM> Clinical SAS Programmer for MAClinical SAS Programmer for MA (60 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> DATALINES within a macro?DATALINES within a macro? (22 lines) From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA> Re: DATALINES within a macro? (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: DATALINES within a macro? (57 lines) From: Charlie Huang <charlie.chao.huang@GMAIL.COM> Re: DATALINES within a macro? (83 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (41 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: DATALINES within a macro? (44 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: DATALINES within a macro? (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: DATALINES within a macro? (69 lines) From: Arthur Tabachneck <art297@ROGERS.COM> DF in mixed models with repeated measuresDF in mixed models with repeated measures (65 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: DF in mixed models with repeated measures (110 lines) From: Robin R High <rhigh@UNMC.EDU> Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
A data manupulation QuestionA data manupulation Question (32 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (41 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (81 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (80 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (81 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A data manupulation Question (96 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (25 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (31 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A data manupulation Question (38 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A data manupulation Question (48 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: A data manupulation Question (60 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Automatic reply: A Count problem has been changed based upon stat decision - Need helpAutomatic reply: A Count problem has been changed based upon stat decision - Need help (20 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607)Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607) (13 lines) From: Erika Steinmetz <esteinmetz@AAMC.ORG> Automatic reply: creating new variables from variable names stored in another variableAutomatic reply: creating new variables from variable names stored in another variable (12 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Batch SAS when both 9.1 and 9.2 existBatch SAS when both 9.1 and 9.2 exist (35 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Batch SAS when both 9.1 and 9.2 exist (55 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Batch SAS when both 9.1 and 9.2 exist (77 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Batch SAS when both 9.1 and 9.2 exist (46 lines) From: Andrew Hansen <hansen.andrew.e@GMAIL.COM> Re: Batch SAS when both 9.1 and 9.2 exist (15 lines) From: Lorne Klassen <lk1@ROGERS.COM> Clinical SAS Programmer for MAClinical SAS Programmer for MA (60 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> DATALINES within a macro?DATALINES within a macro? (22 lines) From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA> Re: DATALINES within a macro? (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: DATALINES within a macro? (57 lines) From: Charlie Huang <charlie.chao.huang@GMAIL.COM> Re: DATALINES within a macro? (83 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (41 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: DATALINES within a macro? (44 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: DATALINES within a macro? (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: DATALINES within a macro? (69 lines) From: Arthur Tabachneck <art297@ROGERS.COM> DF in mixed models with repeated measuresDF in mixed models with repeated measures (65 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: DF in mixed models with repeated measures (110 lines) From: Robin R High <rhigh@UNMC.EDU> Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Automatic reply: A Count problem has been changed based upon stat decision - Need helpAutomatic reply: A Count problem has been changed based upon stat decision - Need help (20 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607)Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607) (13 lines) From: Erika Steinmetz <esteinmetz@AAMC.ORG> Automatic reply: creating new variables from variable names stored in another variableAutomatic reply: creating new variables from variable names stored in another variable (12 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Batch SAS when both 9.1 and 9.2 existBatch SAS when both 9.1 and 9.2 exist (35 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Batch SAS when both 9.1 and 9.2 exist (55 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Batch SAS when both 9.1 and 9.2 exist (77 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Batch SAS when both 9.1 and 9.2 exist (46 lines) From: Andrew Hansen <hansen.andrew.e@GMAIL.COM> Re: Batch SAS when both 9.1 and 9.2 exist (15 lines) From: Lorne Klassen <lk1@ROGERS.COM> Clinical SAS Programmer for MAClinical SAS Programmer for MA (60 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> DATALINES within a macro?DATALINES within a macro? (22 lines) From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA> Re: DATALINES within a macro? (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: DATALINES within a macro? (57 lines) From: Charlie Huang <charlie.chao.huang@GMAIL.COM> Re: DATALINES within a macro? (83 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (41 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: DATALINES within a macro? (44 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: DATALINES within a macro? (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: DATALINES within a macro? (69 lines) From: Arthur Tabachneck <art297@ROGERS.COM> DF in mixed models with repeated measuresDF in mixed models with repeated measures (65 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: DF in mixed models with repeated measures (110 lines) From: Robin R High <rhigh@UNMC.EDU> Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607)Automatic reply: SAS-L Digest - 17 Jun 2011 - Special issue (#2011-607) (13 lines) From: Erika Steinmetz <esteinmetz@AAMC.ORG> Automatic reply: creating new variables from variable names stored in another variableAutomatic reply: creating new variables from variable names stored in another variable (12 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Batch SAS when both 9.1 and 9.2 existBatch SAS when both 9.1 and 9.2 exist (35 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Batch SAS when both 9.1 and 9.2 exist (55 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Batch SAS when both 9.1 and 9.2 exist (77 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Batch SAS when both 9.1 and 9.2 exist (46 lines) From: Andrew Hansen <hansen.andrew.e@GMAIL.COM> Re: Batch SAS when both 9.1 and 9.2 exist (15 lines) From: Lorne Klassen <lk1@ROGERS.COM> Clinical SAS Programmer for MAClinical SAS Programmer for MA (60 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> DATALINES within a macro?DATALINES within a macro? (22 lines) From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA> Re: DATALINES within a macro? (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: DATALINES within a macro? (57 lines) From: Charlie Huang <charlie.chao.huang@GMAIL.COM> Re: DATALINES within a macro? (83 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (41 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: DATALINES within a macro? (44 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: DATALINES within a macro? (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: DATALINES within a macro? (69 lines) From: Arthur Tabachneck <art297@ROGERS.COM> DF in mixed models with repeated measuresDF in mixed models with repeated measures (65 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: DF in mixed models with repeated measures (110 lines) From: Robin R High <rhigh@UNMC.EDU> Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Automatic reply: creating new variables from variable names stored in another variableAutomatic reply: creating new variables from variable names stored in another variable (12 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Batch SAS when both 9.1 and 9.2 existBatch SAS when both 9.1 and 9.2 exist (35 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Batch SAS when both 9.1 and 9.2 exist (55 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Batch SAS when both 9.1 and 9.2 exist (77 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Batch SAS when both 9.1 and 9.2 exist (46 lines) From: Andrew Hansen <hansen.andrew.e@GMAIL.COM> Re: Batch SAS when both 9.1 and 9.2 exist (15 lines) From: Lorne Klassen <lk1@ROGERS.COM> Clinical SAS Programmer for MAClinical SAS Programmer for MA (60 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> DATALINES within a macro?DATALINES within a macro? (22 lines) From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA> Re: DATALINES within a macro? (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: DATALINES within a macro? (57 lines) From: Charlie Huang <charlie.chao.huang@GMAIL.COM> Re: DATALINES within a macro? (83 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (41 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: DATALINES within a macro? (44 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: DATALINES within a macro? (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: DATALINES within a macro? (69 lines) From: Arthur Tabachneck <art297@ROGERS.COM> DF in mixed models with repeated measuresDF in mixed models with repeated measures (65 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: DF in mixed models with repeated measures (110 lines) From: Robin R High <rhigh@UNMC.EDU> Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Batch SAS when both 9.1 and 9.2 existBatch SAS when both 9.1 and 9.2 exist (35 lines) From: Lorne Klassen <lk1@ROGERS.COM> Re: Batch SAS when both 9.1 and 9.2 exist (55 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Batch SAS when both 9.1 and 9.2 exist (77 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: Batch SAS when both 9.1 and 9.2 exist (46 lines) From: Andrew Hansen <hansen.andrew.e@GMAIL.COM> Re: Batch SAS when both 9.1 and 9.2 exist (15 lines) From: Lorne Klassen <lk1@ROGERS.COM> Clinical SAS Programmer for MAClinical SAS Programmer for MA (60 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> DATALINES within a macro?DATALINES within a macro? (22 lines) From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA> Re: DATALINES within a macro? (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: DATALINES within a macro? (57 lines) From: Charlie Huang <charlie.chao.huang@GMAIL.COM> Re: DATALINES within a macro? (83 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (41 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: DATALINES within a macro? (44 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: DATALINES within a macro? (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: DATALINES within a macro? (69 lines) From: Arthur Tabachneck <art297@ROGERS.COM> DF in mixed models with repeated measuresDF in mixed models with repeated measures (65 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: DF in mixed models with repeated measures (110 lines) From: Robin R High <rhigh@UNMC.EDU> Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Clinical SAS Programmer for MAClinical SAS Programmer for MA (60 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> DATALINES within a macro?DATALINES within a macro? (22 lines) From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA> Re: DATALINES within a macro? (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: DATALINES within a macro? (57 lines) From: Charlie Huang <charlie.chao.huang@GMAIL.COM> Re: DATALINES within a macro? (83 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (41 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: DATALINES within a macro? (44 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: DATALINES within a macro? (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: DATALINES within a macro? (69 lines) From: Arthur Tabachneck <art297@ROGERS.COM> DF in mixed models with repeated measuresDF in mixed models with repeated measures (65 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: DF in mixed models with repeated measures (110 lines) From: Robin R High <rhigh@UNMC.EDU> Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
DATALINES within a macro?DATALINES within a macro? (22 lines) From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA> Re: DATALINES within a macro? (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (34 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: DATALINES within a macro? (57 lines) From: Charlie Huang <charlie.chao.huang@GMAIL.COM> Re: DATALINES within a macro? (83 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: DATALINES within a macro? (41 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: DATALINES within a macro? (44 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: DATALINES within a macro? (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: DATALINES within a macro? (69 lines) From: Arthur Tabachneck <art297@ROGERS.COM> DF in mixed models with repeated measuresDF in mixed models with repeated measures (65 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: DF in mixed models with repeated measures (110 lines) From: Robin R High <rhigh@UNMC.EDU> Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
DF in mixed models with repeated measuresDF in mixed models with repeated measures (65 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: DF in mixed models with repeated measures (110 lines) From: Robin R High <rhigh@UNMC.EDU> Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Determine % of ids in one list not in anotherDetermine % of ids in one list not in another (76 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Determine % of ids in one list not in another (110 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Determine % of ids in one list not in another (85 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: Determine % of ids in one list not in another (125 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
ExcelXP ODS Tagset QuestionExcelXP ODS Tagset Question (13 lines) From: jack quin <qinlixun@GMAIL.COM> Re: ExcelXP ODS Tagset Question (25 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ExcelXP ODS Tagset Question (50 lines) From: Sharat Sharma <sharat.katz@GMAIL.COM> Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Exporting SAS GIS Map to an HTML FileExporting SAS GIS Map to an HTML File (17 lines) From: rajiv gumpina <g.rajivkumar@GMAIL.COM> FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
FW: Batch SAS when both 9.1 and 9.2 existFW: Batch SAS when both 9.1 and 9.2 exist (65 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Getting Unique Values each timeGetting Unique Values each time (24 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: Getting Unique Values each time (60 lines) From: Joe Matise <snoopy369@GMAIL.COM> IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
IFC evaluates all arguments before decidingIFC evaluates all arguments before deciding (87 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: IFC evaluates all arguments before deciding (56 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: IFC evaluates all arguments before deciding (94 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: IFC evaluates all arguments before deciding (128 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Importing CSV file saved from Excel containing Alt-Enter charactersImporting CSV file saved from Excel containing Alt-Enter characters (90 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (221 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing CSV file saved from Excel containing Alt-Enter characters (119 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Importing CSV file saved from Excel containing Alt-Enter characters (41 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (25 lines) From: Scott Bass <sas_l_739@YAHOO.COM.AU> Re: Importing CSV file saved from Excel containing Alt-Enter characters (122 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Importing CSV file saved from Excel containing Alt-Enter characters (64 lines) From: Data _null_; <iebupdte@GMAIL.COM> Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Installation of SAS-callable SUDAANInstallation of SAS-callable SUDAAN (45 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Making SAS 9.2 software available via IntranetMaking SAS 9.2 software available via Intranet (32 lines) From: Clare Gill <clare.gill@UCD.IE> Re: Making SAS 9.2 software available via Intranet (59 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Making SAS 9.2 software available via Intranet (52 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: Making SAS 9.2 software available via Intranet (87 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Making SAS 9.2 software available via Intranet (118 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
NJ SAS Users Group Meeting - Friday, July 8thNJ SAS Users Group Meeting - Friday, July 8th (37 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> Re: NJ SAS Users Group Meeting - Friday, July 8th (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> NJ SAS Users Group Meeting - Friday, July 8th (38 lines) From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM> PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
PROC SUMMARY calculating _TYPE_.PROC SUMMARY calculating _TYPE_. (16 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (31 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: PROC SUMMARY calculating _TYPE_. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (27 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC SUMMARY calculating _TYPE_. (20 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: PROC SUMMARY calculating _TYPE_. (57 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: PROC SUMMARY calculating _TYPE_. (63 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: PROC SUMMARY calculating _TYPE_. (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: PROC SUMMARY calculating _TYPE_. (83 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Possible SAS jobs in the Washington, DC, areaPossible SAS jobs in the Washington, DC, area (75 lines) From: Nat Wooding <nathani@VERIZON.NET> Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Proc Surveyselect question regarding sample size for simple random sampleProc Surveyselect question regarding sample size for simple random sample (30 lines) From: Randall Powers <powers_r@BLS.GOV> Re: Proc Surveyselect question regarding sample size for simple random sample (42 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Proc Surveyselect question regarding sample size for simple random sample (58 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Proc Surveyselect question regarding sample size for simple random sample (60 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Referring Back to FilenameReferring Back to Filename (31 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Referring Back to Filename (48 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Referring Back to Filename (10 lines) From: Brian Trautman <btrautman84@GMAIL.COM> Re: Referring Back to Filename (22 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Referring Back to Filename (26 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Rename Variable in PROC SQL XXXXRename Variable in PROC SQL XXXX (25 lines) From: Dan Abner <dan.abner99@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (41 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Rename Variable in PROC SQL XXXX (62 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Rename Variable in PROC SQL XXXX (35 lines) From: Arthur Tabachneck <art297@ROGERS.COM> SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
SAS IML Error: Segmentation Violation In Task [ IML (2) ]Re: SAS IML Error: Segmentation Violation In Task [ IML (2) ] (22 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
SQL pass through Oracle date?SQL pass through Oracle date? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: SQL pass through Oracle date? (34 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: SQL pass through Oracle date? (50 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: SQL pass through Oracle date? (28 lines) From: Ben Ben <benpub7@YAHOO.COM> Re: SQL pass through Oracle date? (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (93 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (142 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (37 lines) From: Mary <mlhoward@AVALON.NET> Re: SQL pass through Oracle date? (44 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: SQL pass through Oracle date? (62 lines) From: Barkanic, Gema HHHH <Gema.Barkanic@CIGNA.COM> Re: SQL pass through Oracle date? (63 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Sample size for repeated logistic regressionSample size for repeated logistic regression (14 lines) From: Michelle Secic <consult@SECICSTATS.COM> Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Somewhat OT: Length=0 Oracle column cause troubleSomewhat OT: Length=0 Oracle column cause trouble (35 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (55 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (69 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (120 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (93 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: Somewhat OT: Length=0 Oracle column cause trouble (78 lines) From: Mary <mlhoward@AVALON.NET> The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN StatementsThe efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (34 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (96 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (181 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (206 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (9 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (150 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (15 lines) From: Seung-min Baek <760105@HANMAIL.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (37 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: The efficient difference of the IF-THEN/ELSE Statements and SELECT/WHEN Statements (23 lines) From: Seung-min Baek <760105@HANMAIL.NET> Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Unix superscript (b)Unix superscript (b) (13 lines) From: John Mike <sasslick@GMAIL.COM> Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Urgent NEED - SAS Programming opportunity in MassachusettsUrgent NEED - SAS Programming opportunity in Massachusetts (40 lines) From: Beverly Godleski <beverly@FPCPINEHURST.COM> Re: Urgent NEED - SAS Programming opportunity in Massachusetts (48 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its ValuesUsing PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (12 lines) From: David Friedman <harrypotterdhf@EARTHLINK.NET> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (35 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (47 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using PROC CONTENTS to Deterimine Which Datasets Have a Certain Variable and Its Values (180 lines) From: Data _null_; <iebupdte@GMAIL.COM> calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
calling WinZip to zip output data from a SAS programRe: calling WinZip to zip output data from a SAS program (63 lines) From: Dai, Randy <Randy.Dai@ASTRAZENECA.COM> censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
censored independent variable?Re: censored independent variable? (67 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: censored independent variable? (63 lines) From: Xin Wei <xinwei@STAT.PSU.EDU> Re: censored independent variable? (87 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: censored independent variable? (82 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: censored independent variable? (88 lines) From: oloolo <dynamicpanel@YAHOO.COM> Re: censored independent variable? (88 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
compare multi variables' valuescompare multi variables' values (13 lines) From: df ss <tggsun@YAHOO.COM> Re: compare multi variables' values (32 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (25 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
creating new variables from variable names stored in another variablecreating new variables from variable names stored in another variable (99 lines) From: Sally Vegso <Sally.Vegso@YALE.EDU> Re: creating new variables from variable names stored in another variable (54 lines) From: Fareeza Khurshed <fkhurshed@GMAIL.COM> Re: creating new variables from variable names stored in another variable (59 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
defining Value and then split accordinglydefining Value and then split accordingly (36 lines) From: Pari <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (75 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: defining Value and then split accordingly (116 lines) From: Pareen Patel <mditconsult@GMAIL.COM> Re: defining Value and then split accordingly (150 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
finding maximum of multiple variables over multiple date windowsfinding maximum of multiple variables over multiple date windows (78 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (89 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (141 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: finding maximum of multiple variables over multiple date windows (171 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: finding maximum of multiple variables over multiple date windows (266 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (285 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: finding maximum of multiple variables over multiple date windows (453 lines) From: Arthur Tabachneck <art297@ROGERS.COM> iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
iso 8601 for duration in hoursiso 8601 for duration in hours (14 lines) From: E P <evp_sasl@YAHOO.CA> Re: iso 8601 for duration in hours (36 lines) From: Nat Wooding <nathani@VERIZON.NET> Re: iso 8601 for duration in hours (29 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: iso 8601 for duration in hours (28 lines) From: E P <evp_sasl@YAHOO.CA> keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
keep variables based on label informationkeep variables based on label information (12 lines) From: df ss <tggsun@YAHOO.COM> Re: keep variables based on label information (41 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (58 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (77 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: keep variables based on label information (33 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: keep variables based on label information (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: keep variables based on label information (118 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: keep variables based on label information (67 lines) From: df ss <tggsun@YAHOO.COM> macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
macro determine name of calling macromacro determine name of calling macro (59 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (87 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (26 lines) From: Quentin McMullen <qmcmullen.sas@GMAIL.COM> Re: macro determine name of calling macro (48 lines) From: OBrien, Craig <COBrien@CPSC.GOV> Re: macro determine name of calling macro (38 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: macro determine name of calling macro (69 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: macro determine name of calling macro (52 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: macro determine name of calling macro (93 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
make a large and "diversified" data set for benchmarking?make a large and "diversified" data set for benchmarking? (30 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: make a large and "diversified" data set for benchmarking? (94 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: make a large and "diversified" data set for benchmarking? (116 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: make a large and "diversified" data set for benchmarking? (13 lines) From: Rick Wicklin <Rick.Wicklin@SAS.COM> number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
number of observations of this data set: sashelp.PRDSAL2number of observations of this data set: sashelp.PRDSAL2 (65 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: number of observations of this data set: sashelp.PRDSAL2 (88 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: number of observations of this data set: sashelp.PRDSAL2 (86 lines) From: Nat Wooding <nathani@VERIZON.NET> nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
nway option for proc meansnway option for proc means (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: nway option for proc means (58 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: nway option for proc means (99 lines) From: bbser 2009 <bbser2009@GMAIL.COM> problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
problems with SAS merge - character vs numeric variablesproblems with SAS merge - character vs numeric variables (48 lines) From: Alison <alisontetler@YAHOO.COM> Re: problems with SAS merge - character vs numeric variables (64 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: problems with SAS merge - character vs numeric variables (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
problems with locks on stored macrosRe: problems with locks on stored macros (64 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: problems with locks on stored macros (109 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
proc reportRe: proc report (142 lines) From: John Mike <sasslick@GMAIL.COM> Re: proc report (37 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (184 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: proc report (183 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
titles >256 and dictionary.titlestitles >256 and dictionary.titles (46 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (71 lines) From: Data _null_; <iebupdte@GMAIL.COM> what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>
what's going on this code, if then elsewhat's going on this code, if then else (64 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's going on this code, if then else (105 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: what's going on this code, if then else (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM>