<No subject><No subject> (10 lines) From: Nancy Li <nancy_li66@YAHOO.COM> =?windows-1252?Q?Re=3A_Count_data_overdispersion_=E2=80=93_not_due_to_ze?= =?windows-1252?Q?ro_inflation?==?windows-1252?Q?Re=3A_Count_data_overdispersion_=E2=80=93_not_due_to_ze?= =?windows-1252?Q?ro_inflation?= (77 lines) From: R B <ryan.andrew.black@GMAIL.COM> A Data manupulation questionRe: A Data manupulation question (21 lines) From: Mahesh Kumar Peesari <peesari.mahesh@GMAIL.COM> Re: A Data manupulation question (38 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: A Data manupulation question (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> A MAX Function questionA MAX Function question (28 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A MAX Function question (48 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: A MAX Function question (58 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: A MAX Function question (68 lines) From: Ben <benpub7@YAHOO.COM> Re: A MAX Function question (112 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A MAX Function question (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Analytics 2011 - SAS Data Mining ConferenceAnalytics 2011 - SAS Data Mining Conference (15 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> Automatic reply: Proc reportAutomatic reply: Proc report (11 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628)Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636)Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636) (22 lines) From: Carol Olson <Carol.Olson@MEREDITH.COM> Automatic reply: Using Numbers in Macro Do-Loops for DatesAutomatic reply: Using Numbers in Macro Do-Loops for Dates (19 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Building Z-Score calculation for Pediatric Blood PressuresBuilding Z-Score calculation for Pediatric Blood Pressures (30 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Building Z-Score calculation for Pediatric Blood Pressures (17 lines) From: Ben Ben <benpub7@YAHOO.COM> Changing a grid of month by year data to a columnChanging a grid of month by year data to a column (50 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Changing a grid of month by year data to a column (28 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: Changing a grid of month by year data to a column (76 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Count data overdispersion – not due to zero inflationCount data overdispersion – not due to zero inflation (51 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTMLEmbedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
=?windows-1252?Q?Re=3A_Count_data_overdispersion_=E2=80=93_not_due_to_ze?= =?windows-1252?Q?ro_inflation?==?windows-1252?Q?Re=3A_Count_data_overdispersion_=E2=80=93_not_due_to_ze?= =?windows-1252?Q?ro_inflation?= (77 lines) From: R B <ryan.andrew.black@GMAIL.COM> A Data manupulation questionRe: A Data manupulation question (21 lines) From: Mahesh Kumar Peesari <peesari.mahesh@GMAIL.COM> Re: A Data manupulation question (38 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: A Data manupulation question (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> A MAX Function questionA MAX Function question (28 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A MAX Function question (48 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: A MAX Function question (58 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: A MAX Function question (68 lines) From: Ben <benpub7@YAHOO.COM> Re: A MAX Function question (112 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A MAX Function question (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Analytics 2011 - SAS Data Mining ConferenceAnalytics 2011 - SAS Data Mining Conference (15 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> Automatic reply: Proc reportAutomatic reply: Proc report (11 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628)Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636)Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636) (22 lines) From: Carol Olson <Carol.Olson@MEREDITH.COM> Automatic reply: Using Numbers in Macro Do-Loops for DatesAutomatic reply: Using Numbers in Macro Do-Loops for Dates (19 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Building Z-Score calculation for Pediatric Blood PressuresBuilding Z-Score calculation for Pediatric Blood Pressures (30 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Building Z-Score calculation for Pediatric Blood Pressures (17 lines) From: Ben Ben <benpub7@YAHOO.COM> Changing a grid of month by year data to a columnChanging a grid of month by year data to a column (50 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Changing a grid of month by year data to a column (28 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: Changing a grid of month by year data to a column (76 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Count data overdispersion – not due to zero inflationCount data overdispersion – not due to zero inflation (51 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTMLEmbedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
A Data manupulation questionRe: A Data manupulation question (21 lines) From: Mahesh Kumar Peesari <peesari.mahesh@GMAIL.COM> Re: A Data manupulation question (38 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: A Data manupulation question (37 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> A MAX Function questionA MAX Function question (28 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A MAX Function question (48 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: A MAX Function question (58 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: A MAX Function question (68 lines) From: Ben <benpub7@YAHOO.COM> Re: A MAX Function question (112 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A MAX Function question (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Analytics 2011 - SAS Data Mining ConferenceAnalytics 2011 - SAS Data Mining Conference (15 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> Automatic reply: Proc reportAutomatic reply: Proc report (11 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628)Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636)Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636) (22 lines) From: Carol Olson <Carol.Olson@MEREDITH.COM> Automatic reply: Using Numbers in Macro Do-Loops for DatesAutomatic reply: Using Numbers in Macro Do-Loops for Dates (19 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Building Z-Score calculation for Pediatric Blood PressuresBuilding Z-Score calculation for Pediatric Blood Pressures (30 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Building Z-Score calculation for Pediatric Blood Pressures (17 lines) From: Ben Ben <benpub7@YAHOO.COM> Changing a grid of month by year data to a columnChanging a grid of month by year data to a column (50 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Changing a grid of month by year data to a column (28 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: Changing a grid of month by year data to a column (76 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Count data overdispersion – not due to zero inflationCount data overdispersion – not due to zero inflation (51 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTMLEmbedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
A MAX Function questionA MAX Function question (28 lines) From: Tom Smith <need_sas_help@YAHOO.COM> Re: A MAX Function question (48 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: A MAX Function question (58 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: A MAX Function question (68 lines) From: Ben <benpub7@YAHOO.COM> Re: A MAX Function question (112 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: A MAX Function question (128 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Analytics 2011 - SAS Data Mining ConferenceAnalytics 2011 - SAS Data Mining Conference (15 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> Automatic reply: Proc reportAutomatic reply: Proc report (11 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628)Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636)Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636) (22 lines) From: Carol Olson <Carol.Olson@MEREDITH.COM> Automatic reply: Using Numbers in Macro Do-Loops for DatesAutomatic reply: Using Numbers in Macro Do-Loops for Dates (19 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Building Z-Score calculation for Pediatric Blood PressuresBuilding Z-Score calculation for Pediatric Blood Pressures (30 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Building Z-Score calculation for Pediatric Blood Pressures (17 lines) From: Ben Ben <benpub7@YAHOO.COM> Changing a grid of month by year data to a columnChanging a grid of month by year data to a column (50 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Changing a grid of month by year data to a column (28 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: Changing a grid of month by year data to a column (76 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Count data overdispersion – not due to zero inflationCount data overdispersion – not due to zero inflation (51 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTMLEmbedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Analytics 2011 - SAS Data Mining ConferenceAnalytics 2011 - SAS Data Mining Conference (15 lines) From: Vincent Granville <vincentg@DATASHAPING.COM> Automatic reply: Proc reportAutomatic reply: Proc report (11 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628)Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636)Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636) (22 lines) From: Carol Olson <Carol.Olson@MEREDITH.COM> Automatic reply: Using Numbers in Macro Do-Loops for DatesAutomatic reply: Using Numbers in Macro Do-Loops for Dates (19 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Building Z-Score calculation for Pediatric Blood PressuresBuilding Z-Score calculation for Pediatric Blood Pressures (30 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Building Z-Score calculation for Pediatric Blood Pressures (17 lines) From: Ben Ben <benpub7@YAHOO.COM> Changing a grid of month by year data to a columnChanging a grid of month by year data to a column (50 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Changing a grid of month by year data to a column (28 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: Changing a grid of month by year data to a column (76 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Count data overdispersion – not due to zero inflationCount data overdispersion – not due to zero inflation (51 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTMLEmbedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Automatic reply: Proc reportAutomatic reply: Proc report (11 lines) From: Rick Smith <Ricky_L_Smith@DELL.COM> Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628)Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636)Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636) (22 lines) From: Carol Olson <Carol.Olson@MEREDITH.COM> Automatic reply: Using Numbers in Macro Do-Loops for DatesAutomatic reply: Using Numbers in Macro Do-Loops for Dates (19 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Building Z-Score calculation for Pediatric Blood PressuresBuilding Z-Score calculation for Pediatric Blood Pressures (30 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Building Z-Score calculation for Pediatric Blood Pressures (17 lines) From: Ben Ben <benpub7@YAHOO.COM> Changing a grid of month by year data to a columnChanging a grid of month by year data to a column (50 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Changing a grid of month by year data to a column (28 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: Changing a grid of month by year data to a column (76 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Count data overdispersion – not due to zero inflationCount data overdispersion – not due to zero inflation (51 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTMLEmbedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628)Automatic reply: SAS-L Digest - 23 Jun 2011 - Special issue (#2011-628) (16 lines) From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU> Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636)Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636) (22 lines) From: Carol Olson <Carol.Olson@MEREDITH.COM> Automatic reply: Using Numbers in Macro Do-Loops for DatesAutomatic reply: Using Numbers in Macro Do-Loops for Dates (19 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Building Z-Score calculation for Pediatric Blood PressuresBuilding Z-Score calculation for Pediatric Blood Pressures (30 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Building Z-Score calculation for Pediatric Blood Pressures (17 lines) From: Ben Ben <benpub7@YAHOO.COM> Changing a grid of month by year data to a columnChanging a grid of month by year data to a column (50 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Changing a grid of month by year data to a column (28 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: Changing a grid of month by year data to a column (76 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Count data overdispersion – not due to zero inflationCount data overdispersion – not due to zero inflation (51 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTMLEmbedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636)Automatic reply: SAS-L Digest - 27 Jun 2011 - Special issue (#2011-636) (22 lines) From: Carol Olson <Carol.Olson@MEREDITH.COM> Automatic reply: Using Numbers in Macro Do-Loops for DatesAutomatic reply: Using Numbers in Macro Do-Loops for Dates (19 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Building Z-Score calculation for Pediatric Blood PressuresBuilding Z-Score calculation for Pediatric Blood Pressures (30 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Building Z-Score calculation for Pediatric Blood Pressures (17 lines) From: Ben Ben <benpub7@YAHOO.COM> Changing a grid of month by year data to a columnChanging a grid of month by year data to a column (50 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Changing a grid of month by year data to a column (28 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: Changing a grid of month by year data to a column (76 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Count data overdispersion – not due to zero inflationCount data overdispersion – not due to zero inflation (51 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTMLEmbedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Automatic reply: Using Numbers in Macro Do-Loops for DatesAutomatic reply: Using Numbers in Macro Do-Loops for Dates (19 lines) From: Jan Squillace <Jan.Squillace@SAS.COM> Building Z-Score calculation for Pediatric Blood PressuresBuilding Z-Score calculation for Pediatric Blood Pressures (30 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Building Z-Score calculation for Pediatric Blood Pressures (17 lines) From: Ben Ben <benpub7@YAHOO.COM> Changing a grid of month by year data to a columnChanging a grid of month by year data to a column (50 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Changing a grid of month by year data to a column (28 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: Changing a grid of month by year data to a column (76 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Count data overdispersion – not due to zero inflationCount data overdispersion – not due to zero inflation (51 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTMLEmbedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Building Z-Score calculation for Pediatric Blood PressuresBuilding Z-Score calculation for Pediatric Blood Pressures (30 lines) From: Chris Bat <darth.pathos@GMAIL.COM> Re: Building Z-Score calculation for Pediatric Blood Pressures (17 lines) From: Ben Ben <benpub7@YAHOO.COM> Changing a grid of month by year data to a columnChanging a grid of month by year data to a column (50 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Changing a grid of month by year data to a column (28 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: Changing a grid of month by year data to a column (76 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Count data overdispersion – not due to zero inflationCount data overdispersion – not due to zero inflation (51 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTMLEmbedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Changing a grid of month by year data to a columnChanging a grid of month by year data to a column (50 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Changing a grid of month by year data to a column (28 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: Changing a grid of month by year data to a column (76 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Count data overdispersion – not due to zero inflationCount data overdispersion – not due to zero inflation (51 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTMLEmbedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Count data overdispersion – not due to zero inflationCount data overdispersion – not due to zero inflation (51 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTMLEmbedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Embedding/Passing throuh HTML to PROC PRINT table results in ODS HTMLEmbedding/Passing throuh HTML to PROC PRINT table results in ODS HTML (27 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Estimate Statement PROC NLMIXEDEstimate Statement PROC NLMIXED (30 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (76 lines) From: R B <ryan.andrew.black@GMAIL.COM> Re: Estimate Statement PROC NLMIXED (137 lines) From: R B <ryan.andrew.black@GMAIL.COM> ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
ExcelXP ODS Tagset QuestionRe: ExcelXP ODS Tagset Question (25 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Hot fix warning - SAS 9.2M3 SolarisHot fix warning - SAS 9.2M3 Solaris (34 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
How to read .dmp filesHow to read .dmp files (20 lines) From: Yusuf Mohamedshah <zulsdad@GMAIL.COM> Re: How to read .dmp files (31 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: How to read .dmp files (78 lines) From: Bian, Haikuo <HBian@NW7.ESRD.NET> Re: How to read .dmp files (91 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
How to use SAS Macro to make data comparisons much more efficient?How to use SAS Macro to make data comparisons much more efficient? (44 lines) From: Tina MayIAsk <tinaask@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (87 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to use SAS Macro to make data comparisons much more efficient? (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Installation of SAS-callable SUDAANRe: Installation of SAS-callable SUDAAN (58 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (63 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Re: Installation of SAS-callable SUDAAN (88 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Installation of SAS-callable SUDAAN (96 lines) From: Garrido, Melissa <melissa.garrido@MSSM.EDU> Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Installing SASInstalling SAS (22 lines) From: fmwan@AOL.COM Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Job Opportunities in the Washington, DC AreaJob Opportunities in the Washington, DC Area (147 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Job Opportunity / TS Clearance required / Northern VAJob Opportunity / TS Clearance required / Northern VA (35 lines) From: Gary McQuown <mcquown@DASCONSULTANTS.COM> Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Job announcement on linkedinJob announcement on linkedin (13 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Long text fields in ExcelRe: Long text fields in Excel (178 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
MergeMerge (30 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (16 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: Merge (44 lines) From: sas8832@HOTMAIL.CO.UK Re: Merge (81 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Minus sign hex code?Minus sign hex code? (15 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: Minus sign hex code? (18 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Minus sign hex code? (51 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
NLMIXED for a DID modelNLMIXED for a DID model (41 lines) From: Ray Harvey <rharvey3015@GMAIL.COM> Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Need help with Bringing in SAS Formats from Mainframes to Unix ServerNeed help with Bringing in SAS Formats from Mainframes to Unix Server (21 lines) From: Pradeep <chittiprolupradeep@GMAIL.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (30 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (38 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (43 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (59 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (126 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Need help with Bringing in SAS Formats from Mainframes to Unix Server (84 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
New Yok SUGNew Yok SUG (31 lines) From: David Kellerman <dak9057@NYP.ORG> Re: New Yok SUG (50 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
ODS output to excel sheetsODS output to excel sheets (81 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (94 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS output to excel sheets (76 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS output to excel sheets (103 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (130 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> Re: ODS output to excel sheets (137 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (135 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: ODS output to excel sheets (159 lines) From: Niklas Wagman <Niklas.Wagman@SAS.SE> OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
OT: Friday HumorOT: Friday Humor (19 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: OT: Friday Humor (27 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: OT: Friday Humor (49 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: OT: Friday Humor (59 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Open Source Reader of SAS Data SetsOpen Source Reader of SAS Data Sets (32 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Open code statement recursion detected, macro codeOpen code statement recursion detected, macro code (38 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (50 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Open code statement recursion detected, macro code (72 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: Open code statement recursion detected, macro code (80 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Open code statement recursion detected, macro code (110 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: Open code statement recursion detected, macro code (159 lines) From: toby dunn <tobydunn@HOTMAIL.COM> PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
PC SAS - Reading jpeg images.PC SAS - Reading jpeg images. (54 lines) From: vasanth s <vasanthz@GMAIL.COM> Re: PC SAS - Reading jpeg images. (87 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (93 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: PC SAS - Reading jpeg images. (103 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: PC SAS - Reading jpeg images. (120 lines) From: vasanth s <vasanthz@GMAIL.COM> PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
PUT functionPUT function (61 lines) From: abderrahim oulhaj <sas58147@GMAIL.COM> Re: PUT function (83 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (78 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: PUT function (141 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: PUT function (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Proc reportProc report (29 lines) From: John Mike <sasslick@GMAIL.COM> Re: Proc report (51 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Raw and Standardized Betas from Proc SurveyregRaw and Standardized Betas from Proc Surveyreg (42 lines) From: Marc Mooney UMN <moon0078@UMN.EDU> Re: Raw and Standardized Betas from Proc Surveyreg (38 lines) From: Jeremy Miles <jeremy.miles@GMAIL.COM> Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Reg: Portal IssueReg: Portal Issue (15 lines) From: amit kumar <amitsasbi@GMAIL.COM> SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
SAS 9.3?Re: SAS 9.3? (15 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: SAS 9.3? (46 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: SAS 9.3? (37 lines) From: Alan Churchill <alan.churchill@PROGNOSINC.COM> SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
SAS Log IssueSAS Log Issue (20 lines) From: Desiree Schaan <desiree.schaan@OCC.TREAS.GOV> SAS Log Issue (42 lines) From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM> Re: SAS Log Issue (11 lines) From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM> Re: SAS Log Issue (54 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SAS Log Issue (54 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
SCL programSCL program (25 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (44 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: SCL program (59 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (65 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: SCL program (81 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: SCL program (100 lines) From: Murphy Choy <goladin@GMAIL.COM> SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
SQL pass through Oracle date?Re: SQL pass through Oracle date? (169 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (83 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: SQL pass through Oracle date? (98 lines) From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV> Re: SQL pass through Oracle date? (116 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: SQL pass through Oracle date? (97 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
STAT problemSTAT problem (22 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (34 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (37 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (44 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (57 lines) From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV> Re: STAT problem (66 lines) From: Steve Denham <stevedrd@YAHOO.COM> Re: STAT problem (78 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (33 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (57 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Re: STAT problem (186 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: STAT problem (97 lines) From: Bhupinder Singh <bhupi80singh@YAHOO.CO.IN> Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Somewhat OT: Length=0 Oracle column cause troubleRe: Somewhat OT: Length=0 Oracle column cause trouble (58 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Tracking SQL progressTracking SQL progress (78 lines) From: David Kellerman <dak9057@NYP.ORG> Re: Tracking SQL progress (101 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Tracking SQL progress (89 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Tracking SQL progress (112 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Uploading SAS to teradataUploading SAS to teradata (17 lines) From: Mona <k_monal_99@YAHOO.COM> Re: Uploading SAS to teradata (86 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
Using Numbers in Macro Do-Loops for DatesUsing Numbers in Macro Do-Loops for Dates (37 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (42 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (78 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (80 lines) From: Myra Oltsik <my0402@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (84 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: Using Numbers in Macro Do-Loops for Dates (67 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: Using Numbers in Macro Do-Loops for Dates (96 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (32 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Using Numbers in Macro Do-Loops for Dates (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
What is "IN" called when used in a merge statement?What is "IN" called when used in a merge statement? (31 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (41 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: What is "IN" called when used in a merge statement? (51 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
code repeated in log wihout further actionscode repeated in log wihout further actions (35 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: code repeated in log wihout further actions (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
column width question in Proc Reportcolumn width question in Proc Report (40 lines) From: sas quest <sasquest@GMAIL.COM> Re: column width question in Proc Report (72 lines) From: Sudo Ku <crafty876@HOTMAIL.COM> compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
compare multi variables' valuesRe: compare multi variables' values (67 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (20 lines) From: Paul D. Hamilton <pdhamilton1@COMCAST.NET> Re: compare multi variables' values (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (51 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (133 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (80 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (175 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (106 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: compare multi variables' values (95 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: compare multi variables' values (179 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (114 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: compare multi variables' values (101 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: compare multi variables' values (114 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: compare multi variables' values (172 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
creating new variables from variable names stored in another variableRe: creating new variables from variable names stored in another variable (102 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
data manipulation helpdata manipulation help (30 lines) From: Michelle Secic <consult@SECICSTATS.COM> Re: data manipulation help (89 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: data manipulation help (34 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (41 lines) From: Mike Jacobsen <nordath1@GMAIL.COM> Re: data manipulation help (39 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: data manipulation help (11 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
dates really messed up in Excel, how to import to SAS?dates really messed up in Excel, how to import to SAS? (31 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (55 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (99 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (217 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (112 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (123 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: dates really messed up in Excel, how to import to SAS? (110 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (125 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: dates really messed up in Excel, how to import to SAS? (182 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (13 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> Re: dates really messed up in Excel, how to import to SAS? (24 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: dates really messed up in Excel, how to import to SAS? (41 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: dates really messed up in Excel, how to import to SAS? (37 lines) From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM> Re: dates really messed up in Excel, how to import to SAS? (43 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
finding maximum of multiple variables over multiple date windowsRe: finding maximum of multiple variables over multiple date windows (502 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> Re: finding maximum of multiple variables over multiple date windows (576 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: finding maximum of multiple variables over multiple date windows (566 lines) From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU> getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
getting the last four numbers as name of data setgetting the last four numbers as name of data set (28 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: getting the last four numbers as name of data set (55 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: getting the last four numbers as name of data set (62 lines) From: SAS_learner <proccontents@GMAIL.COM> importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
importing messy datesRe: importing messy dates (15 lines) From: Nuria Chapinal <nchapinal@YAHOO.COM> macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
macro quoting functions, comilation vs exectutionmacro quoting functions, comilation vs exectution (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
macro variable inside and outside a macromacro variable inside and outside a macro (93 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: macro variable inside and outside a macro (105 lines) From: bbser 2009 <bbser2009@GMAIL.COM> parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
parMbuffparMbuff (18 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: parMbuff (46 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: parMbuff (55 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
problems with locks on stored macrosRe: problems with locks on stored macros (135 lines) From: White, Svend A. <SvendW@HEALTH.OK.GOV> proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
proc reportproc report (25 lines) From: John Mike <sasslick@GMAIL.COM> pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
pulling text out of a specific string of datapulling text out of a specific string of data (37 lines) From: John Parker <John.V.Parker@KP.ORG> pulling text out of a specific string of data (39 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (80 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (126 lines) From: Kirby, Ted <ted.kirby@LEWIN.COM> Re: pulling text out of a specific string of data (145 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (209 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> Re: pulling text out of a specific string of data (223 lines) From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM> Re: pulling text out of a specific string of data (91 lines) From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV> Re: pulling text out of a specific string of data (161 lines) From: John Parker <John.V.Parker@KP.ORG> Re: pulling text out of a specific string of data (207 lines) From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG> regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
regex questionregex question (35 lines) From: Stephane COLAS <scolas@DATAMETRIC.FR> Re: regex question (94 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: regex question (57 lines) From: Arthur Tabachneck <art297@ROGERS.COM> Re: regex question (18 lines) From: Stephane COLAS <Scolas@DATAMETRIC.FR> sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
sas discussion forums are moving!sas discussion forums are moving! (26 lines) From: Andre Wielki <wielki@INED.FR> the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
the benefit of using parmbuff option with MACROSthe benefit of using parmbuff option with MACROS (53 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (80 lines) From: Jim Groeneveld <jim.1stat@YAHOO.COM> Re: the benefit of using parmbuff option with MACROS (100 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (71 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: the benefit of using parmbuff option with MACROS (111 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
titles >256 and dictionary.titlesRe: titles >256 and dictionary.titles (103 lines) From: Ken Borowiak <evilpettingzoo97@AOL.COM> Re: titles >256 and dictionary.titles (113 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: titles >256 and dictionary.titles (120 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: titles >256 and dictionary.titles (127 lines) From: Data _null_; <iebupdte@GMAIL.COM> weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
weird log notesweird log notes (71 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: weird log notes (81 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: weird log notes (78 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: weird log notes (97 lines) From: bbser 2009 <bbser2009@GMAIL.COM> what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>
what's wrong with adding %str(,), parmbuffwhat's wrong with adding %str(,), parmbuff (37 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (58 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (102 lines) From: bbser 2009 <bbser2009@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (107 lines) From: Tom Abernathy <tom.abernathy@GMAIL.COM> Re: what's wrong with adding %str(,), parmbuff (127 lines) From: bbser 2009 <bbser2009@GMAIL.COM>