Table of contents:

• A "non-printing" character that really doesn't print? (4 messages)
• A FOREACH-type operation on a dataset's variables (7 messages)
• A Possible Replacement for SAS Learning Edition (32 messages)
• Any tricks for Annotating HBAR with >32 character midpoint values ?
• Automatic reply: SAS-L Digest - 17 May 2011 - Special issue (#2011-518)
• CSV TagSet question (8 messages)
• Chance to Make SAS-L History: Did You Know That... (7 messages)
• Coding chemotherapy regimens based on single agents (2 messages)
• Cross-sectional/longitudinal effects
• Data Imputation (6 messages)
• Data Truncating (4 messages)
• Data step hash question (nested hash?) (7 messages)
• Does DDE work in Excel 2010? (2 messages)
• Does SAS really process data one record at a time? (5 messages)
• Drug Switching (27 messages)
• FF unable to display images from SAS HTML output
• FW: Does DDE work in Excel 2010? (2 messages)
• General considerations for efficient downloading data from Oracle via SAS/access to Oracle? (9 messages)
• How can I run a sas program using libname statement?
• How can i run a sas program using libname statement? (4 messages)
• How many of you want a SAS implementation of ElasticNet algorithm? (14 messages)
• IMSL Statistical Libraries (4 messages)
• Importing datasets using SAS Enterprise Guide (3 messages)
• Interesting statistics problem related to regression (2 messages)
• Introduction to R begins May 27 2011
• Job: SAS Administrator (Portland, OR)
• Logistic Regression low response rate actions (11 messages)
• Macro Help Needed
• New York Area SAS USERS Group Meeting --June 2 8:30am-5PM
• New York SAS Users Group Meeting -- June 2 8:30am (Revised)
• New variable from string (18 messages)
• ODM Import using SAS
• ONLINE SUMMER COURSES USING R: Statistical Research Analyses I and II
• OT: Monday Humor
• OT: Thursday Theory
• PROC CORR; (weighted spearman correlations) (2 messages)
• PROC IMPORT - Tab Delimited Problem (4 messages)
• PROC MEANS/WEIGHTS - any way to output normalised weight values? (15 messages)
• Patients who are in either of three tables (6 messages)
• Power Analysis (3 messages)
• Presentation question for RUGs and SGF - SAS datasets or other data? (7 messages)
• Problem with comma delimiter while importing data into SAS (through Access) (5 messages)
• Proc report question (2 messages)
• Purchasing academic SAS license directly form SAS (5 messages)
• Question about SAS (3 messages)
• Quick Question - SG graphics (2 messages)
• Read ZigZag data from File (2 messages)
• Regarding Titles with unicode symbols and SAS/Graph
• Regular expression help needed (3 messages)
• Required Help (2 messages)
• SAS connect Sybase (3 messages)
• SAS connect Sybase SQL anywhere
• SASHELP.VTABLE error (10 messages)
• Searching for Who, What, When, Where, and Why on Support.sas.com
• Slightly OT, But Still SAS Related (14 messages)
• Timezone information in MSSQL timestamps: Extraction and manipulation (2 messages)
• Tiny Variance - Problem?
• Truncation Warning in V9.2 (15 messages)
• call symput, what's wrong (5 messages)
• date formats (4 messages)
• macro to fit models in NLMIXED
• nonexistent index, strange result (4 messages)
• preliminary estimation in PROC ARIMA
• problem installing both 32-bit and 64-bit SAS 9.2 on Windows 7 x64 (3 messages)
• reading text in multiple lines (8 messages)
• strange problem with using IDXNAME = (8 messages)
• terminate a data step once condition met (2 messages)
• text mining analysis and word visualization of pdfs (5 messages)
• time format (5 messages)
• why is this happening?? Proc SQL issues....

1. A "non-printing" character that really doesn't print?
   • A "non-printing" character that really doesn't print? (30 lines)
     From: franwdwyer@googlemail.com <franwdwyer@GOOGLEMAIL.COM>
   • Re: A "non-printing" character that really doesn't print? (40 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: A "non-printing" character that really doesn't print? (41 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: A "non-printing" character that really doesn't print? (63 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>

2. A FOREACH-type operation on a dataset's variables
   • A FOREACH-type operation on a dataset's variables (53 lines)
     From: White, Svend A. <SvendW@HEALTH.OK.GOV>
   • Re: A FOREACH-type operation on a dataset's variables (65 lines)
     From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
   • Re: A FOREACH-type operation on a dataset's variables (74 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: A FOREACH-type operation on a dataset's variables (59 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: A FOREACH-type operation on a dataset's variables (93 lines)
     From: White, Svend A. <SvendW@HEALTH.OK.GOV>
   • Re: A FOREACH-type operation on a dataset's variables (103 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: A FOREACH-type operation on a dataset's variables (94 lines)
     From: White, Svend A. <SvendW@HEALTH.OK.GOV>

3. A Possible Replacement for SAS Learning Edition
   • A Possible Replacement for SAS Learning Edition (38 lines)
     From: Nat Wooding <nathani@VERIZON.NET>
   • Re: A Possible Replacement for SAS Learning Edition (54 lines)
     From: bbser 2009 <bbser2009@GMAIL.COM>
   • Re: A Possible Replacement for SAS Learning Edition (72 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: A Possible Replacement for SAS Learning Edition (67 lines)
     From: Nat Wooding <nathani@VERIZON.NET>
   • Re: A Possible Replacement for SAS Learning Edition (90 lines)
     From: bbser 2009 <bbser2009@GMAIL.COM>
   • Re: A Possible Replacement for SAS Learning Edition (130 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: A Possible Replacement for SAS Learning Edition (113 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: A Possible Replacement for SAS Learning Edition (129 lines)
     From: .. <ajayohri@YAHOO.COM>
   • Re: A Possible Replacement for SAS Learning Edition (179 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: A Possible Replacement for SAS Learning Edition (76 lines)
     From: .. <ajayohri@YAHOO.COM>
   • Re: A Possible Replacement for SAS Learning Edition (20 lines)
     From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM>
   • Re: A Possible Replacement for SAS Learning Edition (187 lines)
     From: oloolo <dynamicpanel@YAHOO.COM>
   • Re: A Possible Replacement for SAS Learning Edition (37 lines)
     From: Nat Wooding <nathani@VERIZON.NET>
   • Re: A Possible Replacement for SAS Learning Edition (56 lines)
     From: oloolo <dynamicpanel@YAHOO.COM>
   • Re: A Possible Replacement for SAS Learning Edition (81 lines)
     From: OBrien, Craig <COBrien@CPSC.GOV>
   • Re: A Possible Replacement for SAS Learning Edition (101 lines)
     From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
   • Re: A Possible Replacement for SAS Learning Edition (96 lines)
     From: oloolo <dynamicpanel@YAHOO.COM>
   • Re: A Possible Replacement for SAS Learning Edition (208 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: A Possible Replacement for SAS Learning Edition (118 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: A Possible Replacement for SAS Learning Edition (120 lines)
     From: oloolo <dynamicpanel@YAHOO.COM>
   • Re: A Possible Replacement for SAS Learning Edition (40 lines)
     From: Sierra Info Services/Andrew Karp <andrew@SIERRAINFORMATION.COM>
   • Re: A Possible Replacement for SAS Learning Edition (145 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: A Possible Replacement for SAS Learning Edition (24 lines)
     From: Kevin Myers <kmyers1@CLEARWIRE.NET>
   • Re: A Possible Replacement for SAS Learning Edition (65 lines)
     From: Burton, Ray <Ray.Burton@ACS-INC.COM>
   • Re: A Possible Replacement for SAS Learning Edition (119 lines)
     From: OBrien, Craig <COBrien@CPSC.GOV>
   • Re: A Possible Replacement for SAS Learning Edition (71 lines)
     From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
   • Re: A Possible Replacement for SAS Learning Edition (130 lines)
     From: oloolo <dynamicpanel@YAHOO.COM>
   • Re: A Possible Replacement for SAS Learning Edition (118 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>
   • Re: A Possible Replacement for SAS Learning Edition (20 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: A Possible Replacement for SAS Learning Edition (29 lines)
     From: oloolo <dynamicpanel@YAHOO.COM>
   • Re: A Possible Replacement for SAS Learning Edition (50 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: A Possible Replacement for SAS Learning Edition (50 lines)
     From: oloolo <dynamicpanel@YAHOO.COM>

4. Any tricks for Annotating HBAR with >32 character midpoint values ?
   • Re: Any tricks for Annotating HBAR with >32 character midpoint values ? (30 lines)
     From: Richard DeVenezia <rdevenezia@GMAIL.COM>

5. Automatic reply: SAS-L Digest - 17 May 2011 - Special issue (#2011-518)
   • Automatic reply: SAS-L Digest - 17 May 2011 - Special issue (#2011-518) (13 lines)
     From: Mahadocon, Kristi <kmahadocon@SUNESIS.COM>

6. CSV TagSet question
   • CSV TagSet question (42 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • CSV TagSet question (14 lines)
     From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM>
   • Re: CSV TagSet question (63 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: CSV TagSet question (102 lines)
     From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM>
   • Re: CSV TagSet question (152 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: CSV TagSet question (106 lines)
     From: Chang Chung <chang_y_chung@HOTMAIL.COM>
   • Re: CSV TagSet question (115 lines)
     From: Tom Abernathy <tom.abernathy@GMAIL.COM>
   • Re: CSV TagSet question (138 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>

7. Chance to Make SAS-L History: Did You Know That...
   • Re: Chance to Make SAS-L History: Did You Know That... (87 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>
   • Re: Chance to Make SAS-L History: Did You Know That... (56 lines)
     From: .. <ajayohri@YAHOO.COM>
   • Re: Chance to Make SAS-L History: Did You Know That... (51 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>
   • Re: Chance to Make SAS-L History: Did You Know That... (61 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Chance to Make SAS-L History: Did You Know That... (14 lines)
     From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM>
   • Re: Chance to Make SAS-L History: Did You Know That... (21 lines)
     From: Jfh@alumni.stanford.org <jfh@STANFORDALUMNI.ORG>
   • Re: Chance to Make SAS-L History: Did You Know That... (59 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>

8. Coding chemotherapy regimens based on single agents
   • Coding chemotherapy regimens based on single agents (71 lines)
     From: Paul Miller <pjmiller_57@YAHOO.COM>
   • Re: Coding chemotherapy regimens based on single agents (130 lines)
     From: Paul Miller <pjmiller_57@YAHOO.COM>

9. Cross-sectional/longitudinal effects
   • Re: Cross-sectional/longitudinal effects (58 lines)
     From: William Shakespeare <shakespeare_1040@HOTMAIL.COM>

10. Data Imputation
    • Data Imputation (65 lines)
      From: Paul St Louis <pstloui@DOT.STATE.TX.US>
    • Re: Data Imputation (128 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
    • Re: Data Imputation (14 lines)
      From: Paul St Louis <pstloui@DOT.STATE.TX.US>
    • Re: Data Imputation (62 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
    • Re: Data Imputation (25 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: Data Imputation (32 lines)
      From: Paul St Louis <pstloui@DOT.STATE.TX.US>

11. Data Truncating
    • Data Truncating (39 lines)
      From: SAS Programming <sas@VESERVE.COM>
    • Re: Data Truncating (55 lines)
      From: F J Kelley <jkelley@UGA.EDU>
    • Re: Data Truncating (72 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Data Truncating (76 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>

12. Data step hash question (nested hash?)
    • Re: Data step hash question (nested hash?) (136 lines)
      From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
    • Re: Data step hash question (nested hash?) (61 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: Data step hash question (nested hash?) (159 lines)
      From: Bart Heinsius <bheinsius@GMAIL.COM>
    • Re: Data step hash question (nested hash?) (77 lines)
      From: Bart Heinsius <bheinsius@GMAIL.COM>
    • Re: Data step hash question (nested hash?) (127 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Data step hash question (nested hash?) (199 lines)
      From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
    • Re: Data step hash question (nested hash?) (60 lines)
      From: Richard DeVenezia <rdevenezia@GMAIL.COM>

13. Does DDE work in Excel 2010?
    • Re: Does DDE work in Excel 2010? (83 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: Does DDE work in Excel 2010? (40 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

14. Does SAS really process data one record at a time?
    • Does SAS really process data one record at a time? (33 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Does SAS really process data one record at a time? (82 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: Does SAS really process data one record at a time? (54 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Does SAS really process data one record at a time? (141 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Does SAS really process data one record at a time? (156 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

15. Drug Switching
    • Drug Switching (45 lines)
      From: Dave <david.brewer@UC.EDU>
    • Re: Drug Switching (126 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Drug Switching (161 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Drug Switching (174 lines)
      From: Dave Brewer <david.brewer@UC.EDU>
    • Re: Drug Switching (187 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Drug Switching (193 lines)
      From: Dave <david.brewer@UC.EDU>
    • Re: Drug Switching (206 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Drug Switching (208 lines)
      From: Bian, Haikuo <HBian@NW7.ESRD.NET>
    • Re: Drug Switching (197 lines)
      From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US>
    • Re: Drug Switching (204 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Drug Switching (212 lines)
      From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US>
    • Re: Drug Switching (233 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Drug Switching (227 lines)
      From: Dave Brewer <david.brewer@UC.EDU>
    • Re: Drug Switching (239 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Drug Switching (254 lines)
      From: Dave Brewer <david.brewer@UC.EDU>
    • Re: Drug Switching (263 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Drug Switching (284 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Drug Switching (293 lines)
      From: Dave <david.brewer@UC.EDU>
    • Re: Drug Switching (377 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Drug Switching (336 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Drug Switching (282 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Drug Switching (290 lines)
      From: Dave Brewer <david.brewer@UC.EDU>
    • Re: Drug Switching (400 lines)
      From: Dave <david.brewer@UC.EDU>
    • Re: Drug Switching (346 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Drug Switching (351 lines)
      From: Dave Brewer <david.brewer@UC.EDU>
    • Re: Drug Switching (421 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Drug Switching (429 lines)
      From: Dave Brewer <david.brewer@UC.EDU>

16. FF unable to display images from SAS HTML output
    • FF unable to display images from SAS HTML output (28 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>

17. FW: Does DDE work in Excel 2010?
    • FW: Does DDE work in Excel 2010? (22 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: FW: Does DDE work in Excel 2010? (39 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>

18. General considerations for efficient downloading data from Oracle via SAS/access to Oracle?
    • General considerations for efficient downloading data from Oracle via SAS/access to Oracle? (36 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: General considerations for efficient downloading data from Oracle via SAS/access to Oracle? (51 lines)
      From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US>
    • Re: General considerations for efficient downloading data from Oracle via SAS/access to Oracle? (46 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: General considerations for efficient downloading data from Oracle via SAS/access to Oracle? (61 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: General considerations for efficient downloading data from Oracle via SAS/access to Oracle? (72 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • General considerations for efficient downloading data from Oracle via SAS/access to Oracle? (57 lines)
      From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM>
    • Re: General considerations for efficient downloading data from Oracle via SAS/access to Oracle? (60 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: General considerations for efficient downloading data from Oracle via SAS/access to Oracle? (93 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: General considerations for efficient downloading data from Oracle via SAS/access to Oracle? (116 lines)
      From: Gabriel Rosas <rosas.gabe@GMAIL.COM>

19. How can I run a sas program using libname statement?
    • Re: How can I run a sas program using libname statement? (190 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>

20. How can i run a sas program using libname statement?
    • How can i run a sas program using libname statement? (11 lines)
      From: Tom Smith <need_sas_help@YAHOO.COM>
    • Re: How can i run a sas program using libname statement? (23 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: How can i run a sas program using libname statement? (37 lines)
      From: Tom Smith <need_sas_help@YAHOO.COM>
    • Re: How can i run a sas program using libname statement? (71 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

21. How many of you want a SAS implementation of ElasticNet algorithm?
    • How many of you want a SAS implementation of ElasticNet algorithm? (10 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: How many of you want a SAS implementation of ElasticNet algorithm? (23 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: How many of you want a SAS implementation of ElasticNet algorithm? (41 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: How many of you want a SAS implementation of ElasticNet algorithm? (58 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: How many of you want a SAS implementation of ElasticNet algorithm? (62 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: How many of you want a SAS implementation of ElasticNet algorithm? (81 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: How many of you want a SAS implementation of ElasticNet algorithm? (87 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: How many of you want a SAS implementation of ElasticNet algorithm? (111 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: How many of you want a SAS implementation of ElasticNet algorithm? (127 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: How many of you want a SAS implementation of ElasticNet algorithm? (130 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: How many of you want a SAS implementation of ElasticNet algorithm? (160 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: How many of you want a SAS implementation of ElasticNet algorithm? (165 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: How many of you want a SAS implementation of ElasticNet algorithm? (197 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: How many of you want a SAS implementation of ElasticNet algorithm? (212 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

22. IMSL Statistical Libraries
    • Re: IMSL Statistical Libraries (13 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: IMSL Statistical Libraries (44 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: IMSL Statistical Libraries (24 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: IMSL Statistical Libraries (49 lines)
      From: Murphy Choy <goladin@GMAIL.COM>

23. Importing datasets using SAS Enterprise Guide
    • Importing datasets using SAS Enterprise Guide (43 lines)
      From: Marc Mooney UMN <moon0078@UMN.EDU>
    • Re: Importing datasets using SAS Enterprise Guide (65 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Importing datasets using SAS Enterprise Guide (53 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

24. Interesting statistics problem related to regression
    • Re: Interesting statistics problem related to regression (78 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: Interesting statistics problem related to regression (103 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

25. Introduction to R begins May 27 2011
    • Introduction to R begins May 27 2011 (62 lines)
      From: Dorothy Middleton <courses@STATCOURSE.COM>

26. Job: SAS Administrator (Portland, OR)
    • Job: SAS Administrator (Portland, OR) (10 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

27. Logistic Regression low response rate actions
    • Logistic Regression low response rate actions (15 lines)
      From: Linda Isenhower <lkisenhower@CBEGROUP.COM>
    • Re: Logistic Regression low response rate actions (40 lines)
      From: Jeremy Miles <jeremy.miles@GMAIL.COM>
    • Re: Logistic Regression low response rate actions (34 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: Logistic Regression low response rate actions (61 lines)
      From: Linda Isenhower <Lkisenhower@CBEGROUP.COM>
    • Re: Logistic Regression low response rate actions (71 lines)
      From: Linda Isenhower <Lkisenhower@CBEGROUP.COM>
    • Re: Logistic Regression low response rate actions (31 lines)
      From: .. <ajayohri@YAHOO.COM>
    • Re: Logistic Regression low response rate actions (31 lines)
      From: Jeremy Miles <jeremy.miles@GMAIL.COM>
    • Re: Logistic Regression low response rate actions (65 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Logistic Regression low response rate actions (53 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Logistic Regression low response rate actions (80 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: Logistic Regression low response rate actions (78 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>

28. Macro Help Needed
    • Re: Macro Help Needed (106 lines)
      From: Dave Brewer <david.brewer@UC.EDU>

29. New York Area SAS USERS Group Meeting --June 2 8:30am-5PM
    • New York Area SAS USERS Group Meeting --June 2 8:30am-5PM (87 lines)
      From: Robert Patelsky <rpatelsky@YAHOO.COM>

30. New York SAS Users Group Meeting -- June 2 8:30am (Revised)
    • New York SAS Users Group Meeting -- June 2 8:30am (Revised) (88 lines)
      From: Robert Patelsky <rpatelsky@YAHOO.COM>

31. New variable from string
    • New variable from string (20 lines)
      From: Kline, Aimee R. <Kline.Aimee@MAYO.EDU>
    • Re: New variable from string (60 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: New variable from string (32 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: New variable from string (33 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: New variable from string (59 lines)
      From: Kline, Aimee R. <Kline.Aimee@MAYO.EDU>
    • Re: New variable from string (61 lines)
      From: Kline, Aimee R. <Kline.Aimee@MAYO.EDU>
    • Re: New variable from string (71 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: New variable from string (84 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: New variable from string (58 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: New variable from string (92 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: New variable from string (98 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: New variable from string (80 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: New variable from string (111 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: New variable from string (76 lines)
      From: Kline, Aimee R. <Kline.Aimee@MAYO.EDU>
    • Re: New variable from string (107 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: New variable from string (135 lines)
      From: Kline, Aimee R. <Kline.Aimee@MAYO.EDU>
    • Re: New variable from string (193 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: New variable from string (111 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

32. ODM Import using SAS
    • ODM Import using SAS (20 lines)
      From: Rasesh Patel <rasesh.h.patel@GMAIL.COM>

33. ONLINE SUMMER COURSES USING R: Statistical Research Analyses I and II
    • ONLINE SUMMER COURSES USING R: Statistical Research Analyses I and II (67 lines)
      From: Geoffrey Hubona <ghubona@GMAIL.COM>

34. OT: Monday Humor
    • OT: Monday Humor (41 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

35. OT: Thursday Theory
    • OT: Thursday Theory (21 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

36. PROC CORR; (weighted spearman correlations)
    • Re: PROC CORR; (weighted spearman correlations) (43 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: PROC CORR; (weighted spearman correlations) (65 lines)
      From: Murphy Choy <goladin@GMAIL.COM>

37. PROC IMPORT - Tab Delimited Problem
    • Re: PROC IMPORT - Tab Delimited Problem (221 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: PROC IMPORT - Tab Delimited Problem (252 lines)
      From: Dave <david.brewer@UC.EDU>
    • Re: PROC IMPORT - Tab Delimited Problem (248 lines)
      From: Dave Brewer <david.brewer@UC.EDU>
    • Re: PROC IMPORT - Tab Delimited Problem (264 lines)
      From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM>

38. PROC MEANS/WEIGHTS - any way to output normalised weight values?
    • PROC MEANS/WEIGHTS - any way to output normalised weight values? (24 lines)
      From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (40 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (44 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (40 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (75 lines)
      From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (91 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (148 lines)
      From: Robin R High <rhigh@UNMC.EDU>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (211 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (238 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (288 lines)
      From: Robin R High <rhigh@UNMC.EDU>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (236 lines)
      From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (316 lines)
      From: Robin R High <rhigh@UNMC.EDU>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (327 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (424 lines)
      From: Robin R High <rhigh@UNMC.EDU>
    • Re: PROC MEANS/WEIGHTS - any way to output normalised weight values? (446 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>

39. Patients who are in either of three tables
    • Patients who are in either of three tables (20 lines)
      From: Irin later <irinfigvam@YAHOO.COM>
    • Re: Patients who are in either of three tables (45 lines)
      From: OBrien, Craig <COBrien@CPSC.GOV>
    • Re: Patients who are in either of three tables (43 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Patients who are in either of three tables (38 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Patients who are in either of three tables (53 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: Patients who are in either of three tables (60 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>

40. Power Analysis
    • Power Analysis (18 lines)
      From: Ali Zanaty <zanaty2005@YAHOO.COM>
    • Re: Power Analysis (40 lines)
      From: Dennis Fisher <dfisher@CSULB.EDU>
    • Re: Power Analysis (27 lines)
      From: Fareeza Khurshed <fkhurshed@GMAIL.COM>

41. Presentation question for RUGs and SGF - SAS datasets or other data?
    • Presentation question for RUGs and SGF - SAS datasets or other data? (53 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Presentation question for RUGs and SGF - SAS datasets or other data? (55 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Presentation question for RUGs and SGF - SAS datasets or other data? (18 lines)
      From: Dianne Rhodes <diannerhodes@COMCAST.NET>
    • Re: Presentation question for RUGs and SGF - SAS datasets or other data? (31 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Presentation question for RUGs and SGF - SAS datasets or other data? (79 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Presentation question for RUGs and SGF - SAS datasets or other data? (79 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Presentation question for RUGs and SGF - SAS datasets or other data? (15 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

42. Problem with comma delimiter while importing data into SAS (through Access)
    • Problem with comma delimiter while importing data into SAS (through Access) (50 lines)
      From: Irin later <irinfigvam@YAHOO.COM>
    • Re: Problem with comma delimiter while importing data into SAS (through Access) (106 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Problem with comma delimiter while importing data into SAS (through Access) (67 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Problem with comma delimiter while importing data into SAS (through Access) (10 lines)
      From: Paul St Louis <pstloui@DOT.STATE.TX.US>
    • Re: Problem with comma delimiter while importing data into SAS (through Access) (90 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

43. Proc report question
    • Proc report question (36 lines)
      From: Masoud Pajoh <mpajoh@ODOT.ORG>
    • Re: Proc report question (63 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

44. Purchasing academic SAS license directly form SAS
    • Re: Purchasing academic SAS license directly form SAS (164 lines)
      From: Marc Mooney UMN <moon0078@UMN.EDU>
    • Re: Purchasing academic SAS license directly form SAS (49 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Purchasing academic SAS license directly form SAS (103 lines)
      From: Philip Rack <PhilRack@MINEQUEST.COM>
    • Re: Purchasing academic SAS license directly form SAS (172 lines)
      From: Philip Rack <PhilRack@MINEQUEST.COM>
    • Re: Purchasing academic SAS license directly form SAS (186 lines)
      From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM>

45. Question about SAS
    • Re: Question about SAS (101 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: Question about SAS (119 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: Question about SAS (404 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

46. Quick Question - SG graphics
    • Quick Question - SG graphics (34 lines)
      From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM>
    • Re: Quick Question - SG graphics (46 lines)
      From: Randy Herbison <RandyHerbison@WESTAT.COM>

47. Read ZigZag data from File
    • Read ZigZag data from File (64 lines)
      From: Mahesh <peesari.mahesh@GMAIL.COM>
    • Re: Read ZigZag data from File (154 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

48. Regarding Titles with unicode symbols and SAS/Graph
    • Re: Regarding Titles with unicode symbols and SAS/Graph (33 lines)
      From: John Hendrickx <john2.hendrickx@GMAIL.COM>

49. Regular expression help needed
    • Re: Regular expression help needed (138 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Regular expression help needed (143 lines)
      From: Scott Bass <sas_l_739@YAHOO.COM.AU>
    • Re: Regular expression help needed (209 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>

50. Required Help
    • Required Help (34 lines)
      From: Ronit <dosti5151@YAHOO.CO.IN>
    • Re: Required Help (67 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

51. SAS connect Sybase
    • SAS connect Sybase (14 lines)
      From: df ss <tggsun@YAHOO.COM>
    • SAS connect Sybase (12 lines)
      From: dd sf <ddsf4sas@GMAIL.COM>
    • Re: SAS connect Sybase (21 lines)
      From: dd sf <ddsf4sas@GMAIL.COM>

52. SAS connect Sybase SQL anywhere
    • SAS connect Sybase SQL anywhere (13 lines)
      From: df ss <tggsun@YAHOO.COM>

53. SASHELP.VTABLE error
    • SASHELP.VTABLE error (43 lines)
      From: Andy A <neal@FOLKARTINBOTTLES.COM>
    • Re: SASHELP.VTABLE error (69 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: SASHELP.VTABLE error (65 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: SASHELP.VTABLE error (94 lines)
      From: Andy A <neal@FOLKARTINBOTTLES.COM>
    • Re: SASHELP.VTABLE error (115 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: SASHELP.VTABLE error (132 lines)
      From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM>
    • Re: SASHELP.VTABLE error (147 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: SASHELP.VTABLE error (148 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: SASHELP.VTABLE error (94 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: SASHELP.VTABLE error (86 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

54. Searching for Who, What, When, Where, and Why on Support.sas.com
    • Searching for Who, What, When, Where, and Why on Support.sas.com (56 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

55. Slightly OT, But Still SAS Related
    • Slightly OT, But Still SAS Related (46 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Slightly OT, But Still SAS Related (56 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Slightly OT, But Still SAS Related (25 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Slightly OT, But Still SAS Related (12 lines)
      From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM>
    • Re: Slightly OT, But Still SAS Related (47 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Slightly OT, But Still SAS Related (57 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: Slightly OT, But Still SAS Related (68 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Slightly OT, But Still SAS Related (58 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Slightly OT, But Still SAS Related (90 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Slightly OT, But Still SAS Related (33 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Slightly OT, But Still SAS Related (77 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Slightly OT, But Still SAS Related (115 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Slightly OT, But Still SAS Related (124 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Slightly OT, But Still SAS Related (149 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

56. Timezone information in MSSQL timestamps: Extraction and manipulation
    • Timezone information in MSSQL timestamps: Extraction and manipulation (39 lines)
      From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>
    • Re: Timezone information in MSSQL timestamps: Extraction and manipulation (100 lines)
      From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>

57. Tiny Variance - Problem?
    • Tiny Variance - Problem? (42 lines)
      From: R B <ryan.andrew.black@GMAIL.COM>

58. Truncation Warning in V9.2
    • Truncation Warning in V9.2 (38 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Truncation Warning in V9.2 (50 lines)
      From: John Hendrickx <john2.hendrickx@GMAIL.COM>
    • Re: Truncation Warning in V9.2 (67 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Truncation Warning in V9.2 (55 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Truncation Warning in V9.2 (227 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: Truncation Warning in V9.2 (102 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Truncation Warning in V9.2 (80 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Truncation Warning in V9.2 (114 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Truncation Warning in V9.2 (114 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Truncation Warning in V9.2 (231 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Truncation Warning in V9.2 (124 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Truncation Warning in V9.2 (146 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Truncation Warning in V9.2 (154 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Truncation Warning in V9.2 (178 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Truncation Warning in V9.2 (176 lines)
      From: Robin Templer <templerr@CLEAR.NET.NZ>

59. call symput, what's wrong
    • call symput, what's wrong (71 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: call symput, what's wrong (79 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: call symput, what's wrong (77 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: call symput, what's wrong (141 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: call symput, what's wrong (164 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

60. date formats
    • date formats (22 lines)
      From: Nuria Chapinal <nchapinal@YAHOO.COM>
    • Re: date formats (34 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: date formats (46 lines)
      From: OBrien, Craig <COBrien@CPSC.GOV>
    • Re: date formats (53 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

61. macro to fit models in NLMIXED
    • macro to fit models in NLMIXED (49 lines)
      From: SUBSCRIBE SAS-L Anonymous <latitude68@HOTMAIL.COM>

62. nonexistent index, strange result
    • nonexistent index, strange result (61 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: nonexistent index, strange result (75 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: nonexistent index, strange result (104 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: nonexistent index, strange result (211 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

63. preliminary estimation in PROC ARIMA
    • preliminary estimation in PROC ARIMA (39 lines)
      From: =?UTF-8?B?6aG+6aOe?= <gufei1984@GMAIL.COM>

64. problem installing both 32-bit and 64-bit SAS 9.2 on Windows 7 x64
    • problem installing both 32-bit and 64-bit SAS 9.2 on Windows 7 x64 (18 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: problem installing both 32-bit and 64-bit SAS 9.2 on Windows 7 x64 (39 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: problem installing both 32-bit and 64-bit SAS 9.2 on Windows 7 x64 (37 lines)
      From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>

65. reading text in multiple lines
    • reading text in multiple lines (27 lines)
      From: L... L... <mar.lamack@HOTMAIL.COM>
    • Re: reading text in multiple lines (47 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: reading text in multiple lines (85 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: reading text in multiple lines (57 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • reading text in multiple lines (15 lines)
      From: L... L... <mar.lamack@HOTMAIL.COM>
    • Re: reading text in multiple lines (58 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: reading text in multiple lines (33 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: reading text in multiple lines (65 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>

66. strange problem with using IDXNAME =
    • strange problem with using IDXNAME = (67 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: strange problem with using IDXNAME = (80 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: strange problem with using IDXNAME = (88 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: strange problem with using IDXNAME = (161 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: strange problem with using IDXNAME = (107 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: strange problem with using IDXNAME = (158 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: strange problem with using IDXNAME = (120 lines)
      From: Robin Templer <templerr@CLEAR.NET.NZ>
    • Re: strange problem with using IDXNAME = (175 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

67. terminate a data step once condition met
    • terminate a data step once condition met (29 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: terminate a data step once condition met (37 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

68. text mining analysis and word visualization of pdfs
    • text mining analysis and word visualization of pdfs (26 lines)
      From: Ajay Ohri <ohri2007@GMAIL.COM>
    • Re: text mining analysis and word visualization of pdfs (43 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: text mining analysis and word visualization of pdfs (57 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: text mining analysis and word visualization of pdfs (68 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: text mining analysis and word visualization of pdfs (112 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

69. time format
    • time format (37 lines)
      From: Nuria Chapinal <nchapinal@YAHOO.COM>
    • Re: time format (59 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: time format (72 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: time format (75 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: time format (83 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

70. why is this happening?? Proc SQL issues....
    • Re: why is this happening?? Proc SQL issues.... (9 lines)
      From: SUBSCRIBE SAS-L Anonymous <jason.gannon@YAHOO.COM>