Table of contents:

• After getting all distinct reports,the program will be still running in Enterprise guide
• Ask for helps for working very big DB in SAS
• Automatic reply: SAS-L Digest - 3 Jun 2012 to 4 Jun 2012 (#2012-405)
• Automatic reply: SAS-L Digest - 7 Jun 2012 - Special issue (#2012-418) (2 messages)
• Checking for missingness XXXX (6 messages)
• Conditionally Deleting/Renaming SAS Data Sets (2 messages)
• Crossover study (4 messages)
• DOW loop processing gone wrong
• Data Merge?
• Datastep memory leak? (13 messages)
• Dozen Online R Courses: $110 Total Cost
• Fatal ODS error has occurred. Unable to continue processing this output destination
• Fwd: renaming data sets through loops
• GTL - vectorplot - layout prototype / cycleattrs=true (3 messages)
• Import problem .csv file (2 messages)
• JBOSS equivalent of Apache mod-rewrite ? (2 messages)
• Linux/Unix Disk Caching (5 messages)
• Longitudinal data: proc mixed, proc nlmixed time continuous or discrete? (6 messages)
• Looping a Keyword Parameter (Macro Bundles) (4 messages)
• Modifying a data set by extracting only a few ID's at a time (8 messages)
• New Leadership Council for the SAS Community (4 messages)
• OLEDB Question (4 messages)
• Ordering ID variable after proc transpose (20 messages)
• Outputting Excel comments (12 messages)
• Program still running after getting all PDF reports.
• Proper way to clear output;? (7 messages)
• Reading >255 columns of Excel XLSX file (8 messages)
• Reminder: SGF Comes to Toronto
• Reordering variables (6 messages)
• SAS Help (6 messages)
• SAS Users - Summer Conferences
• SAS and TIOBE (5 messages)
• SQL set operator EXCEPT sorts data? (9 messages)
• Simple long to wide task (8 messages)
• What do if Fatal ODS error has occurred .
• When Two eqauls one.... (2 messages)
• When will we get descriptive statistics out of SQL?
• call symput causes error:Apparent symbolic reference not resolved
• converting Proc sort + Datastep merge into Proc SQL joins (6 messages)
• dataset name parsing macro - does it exist? (3 messages)
• do not compute percent in proc freq out= data set
• how to compare and verify results (2 messages)
• how to hash-object this? (11 messages)
• interaction btw outer and inner queries (5 messages)
• no directory, a shortcomgin of SAS editor? (6 messages)
• renaming data sets through loops (7 messages)
• reset the default program open folder (5 messages)
• selecting multiple samples within one shot (16 messages)
• survival analysis - help (5 messages)

1. After getting all distinct reports,the program will be still running in Enterprise guide
   • After getting all distinct reports,the program will be still running in Enterprise guide (36 lines)
     From: SAS Analyst <analystprasad@YAHOO.CO.IN>

2. Ask for helps for working very big DB in SAS
   • Re: Ask for helps for working very big DB in SAS (219 lines)
     From: Søren Lassen <s.lassen@POST.TELE.DK>

3. Automatic reply: SAS-L Digest - 3 Jun 2012 to 4 Jun 2012 (#2012-405)
   • Automatic reply: SAS-L Digest - 3 Jun 2012 to 4 Jun 2012 (#2012-405) (12 lines)
     From: Charlotte Reemts <creemts@TNC.ORG>

4. Automatic reply: SAS-L Digest - 7 Jun 2012 - Special issue (#2012-418)
   • Automatic reply: SAS-L Digest - 7 Jun 2012 - Special issue (#2012-418) (31 lines)
     From: Kathy Jorgensen <Kathy.Jorgensen@MEREDITH.COM>
   • Automatic reply: SAS-L Digest - 7 Jun 2012 - Special issue (#2012-418) (21 lines)
     From: Carol Olson <Carol.Olson@MEREDITH.COM>

5. Checking for missingness XXXX
   • Checking for missingness XXXX (19 lines)
     From: Dan Abner <dan.abner99@GMAIL.COM>
   • Re: Checking for missingness XXXX (11 lines)
     From: Joseph Hinson <jwhinson@GMAIL.COM>
   • Re: Checking for missingness XXXX (36 lines)
     From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV>
   • Re: Checking for missingness XXXX (41 lines)
     From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
   • Re: Checking for missingness XXXX (83 lines)
     From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
   • Re: Checking for missingness XXXX (45 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>

6. Conditionally Deleting/Renaming SAS Data Sets
   • Re: Conditionally Deleting/Renaming SAS Data Sets (75 lines)
     From: Avi-Gil Chaitovsky <avi-gil.chaitovsky@ANTHEM.COM>
   • Re: Conditionally Deleting/Renaming SAS Data Sets (95 lines)
     From: Nat Wooding <nathani@VERIZON.NET>

7. Crossover study
   • Crossover study (19 lines)
     From: William Shakespeare <shakespeare_1040@HOTMAIL.COM>
   • Re: Crossover study (30 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: Crossover study (30 lines)
     From: William Shakespeare <shakespeare_1040@HOTMAIL.COM>
   • Re: Crossover study (66 lines)
     From: William Shakespeare <shakespeare_1040@HOTMAIL.COM>

8. DOW loop processing gone wrong
   • Re: DOW loop processing gone wrong (122 lines)
     From: Chang Chung <chang_y_chung@HOTMAIL.COM>

9. Data Merge?
   • Re: Data Merge? (77 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>

10. Datastep memory leak?
    • Re: Datastep memory leak? (139 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Datastep memory leak? (130 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Datastep memory leak? (167 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Datastep memory leak? (176 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Datastep memory leak? (178 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Datastep memory leak? (194 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: Datastep memory leak? (186 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Datastep memory leak? (183 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: Datastep memory leak? (210 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Datastep memory leak? (215 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Datastep memory leak? (257 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>
    • Re: Datastep memory leak? (298 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Datastep memory leak? (309 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

11. Dozen Online R Courses: $110 Total Cost
    • Dozen Online R Courses: $110 Total Cost (34 lines)
      From: Geoffrey Hubona <ghubona@GMAIL.COM>

12. Fatal ODS error has occurred. Unable to continue processing this output destination
    • Fatal ODS error has occurred. Unable to continue processing this output destination (156 lines)
      From: SAS Analyst <analystprasad@YAHOO.CO.IN>

13. Fwd: renaming data sets through loops
    • Fwd: renaming data sets through loops (79 lines)
      From: tony tony <tonysingsong@GMAIL.COM>

14. GTL - vectorplot - layout prototype / cycleattrs=true
    • GTL - vectorplot - layout prototype / cycleattrs=true (45 lines)
      From: Philip C <SASL.PhilipC@GMAIL.COM>
    • Re: GTL - vectorplot - layout prototype / cycleattrs=true (58 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>
    • Re: GTL - vectorplot - layout prototype / cycleattrs=true (26 lines)
      From: Philip C <SASL.PhilipC@GMAIL.COM>

15. Import problem .csv file
    • Import problem .csv file (15 lines)
      From: Regine Haardoerfer <regine.haardoerfer@EMORY.EDU>
    • Re: Import problem .csv file (32 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

16. JBOSS equivalent of Apache mod-rewrite ?
    • JBOSS equivalent of Apache mod-rewrite ? (35 lines)
      From: Richard Devenezia <rdevenezia@GMAIL.COM>
    • Re: JBOSS equivalent of Apache mod-rewrite ? (48 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

17. Linux/Unix Disk Caching
    • Linux/Unix Disk Caching (32 lines)
      From: Phil Rack <philrack@MINEQUEST.COM>
    • Re: Linux/Unix Disk Caching (65 lines)
      From: robin Templer <templerr@CLEAR.NET.NZ>
    • Re: Linux/Unix Disk Caching (81 lines)
      From: Phil Rack <philrack@MINEQUEST.COM>
    • Re: Linux/Unix Disk Caching (103 lines)
      From: Sigurd W. Hermansen <hermans1@WESTAT.COM>
    • Re: Linux/Unix Disk Caching (127 lines)
      From: Fried Egg <friedegg2012@GMAIL.COM>

18. Longitudinal data: proc mixed, proc nlmixed time continuous or discrete?
    • Longitudinal data: proc mixed, proc nlmixed time continuous or discrete? (59 lines)
      From: Abdelouahid Tajar <a_tajar@HOTMAIL.CO.UK>
    • Re: Longitudinal data: proc mixed, proc nlmixed time continuous or discrete? (52 lines)
      From: Steve Denham <stevedrd@YAHOO.COM>
    • Re: Longitudinal data: proc mixed, proc nlmixed time continuous or discrete? (92 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: Longitudinal data: proc mixed, proc nlmixed time continuous or discrete? (142 lines)
      From: Abdelouahid Tajar <a_tajar@HOTMAIL.CO.UK>
    • Re: Longitudinal data: proc mixed, proc nlmixed time continuous or discrete? (223 lines)
      From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>
    • Re: Longitudinal data: proc mixed, proc nlmixed time continuous or discrete? (117 lines)
      From: Steve Denham <stevedrd@YAHOO.COM>

19. Looping a Keyword Parameter (Macro Bundles)
    • Looping a Keyword Parameter (Macro Bundles) (47 lines)
      From: Matt Baker <baker.matthew@BLS.GOV>
    • Re: Looping a Keyword Parameter (Macro Bundles) (84 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Looping a Keyword Parameter (Macro Bundles) (99 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Looping a Keyword Parameter (Macro Bundles) (107 lines)
      From: Yuewei Liu <contact@YUEWEILIU.COM>

20. Modifying a data set by extracting only a few ID's at a time
    • Modifying a data set by extracting only a few ID's at a time (43 lines)
      From: Randy <randistan69@HOTMAIL.COM>
    • Re: Modifying a data set by extracting only a few ID's at a time (9 lines)
      From: Sai Venkat <chsv.1983@GMAIL.COM>
    • Re: Modifying a data set by extracting only a few ID's at a time (69 lines)
      From: Mahesh Kumar <peesari.mahesh@GMAIL.COM>
    • Re: Modifying a data set by extracting only a few ID's at a time (71 lines)
      From: Randy <randistan69@HOTMAIL.COM>
    • Re: Modifying a data set by extracting only a few ID's at a time (61 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Modifying a data set by extracting only a few ID's at a time (80 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Modifying a data set by extracting only a few ID's at a time (62 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: Modifying a data set by extracting only a few ID's at a time (76 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

21. New Leadership Council for the SAS Community
    • New Leadership Council for the SAS Community (44 lines)
      From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM>
    • Re: New Leadership Council for the SAS Community (83 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: New Leadership Council for the SAS Community (71 lines)
      From: J. Philip Miller <phil@WUBIOS.WUSTL.EDU>
    • Re: New Leadership Council for the SAS Community (79 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>

22. OLEDB Question
    • OLEDB Question (67 lines)
      From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>
    • Re: OLEDB Question (75 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: OLEDB Question (105 lines)
      From: Chris Hemedinger <Chris.Hemedinger@SAS.COM>
    • Re: OLEDB Question (100 lines)
      From: DUELL, BOB <bd9439@ATT.COM>

23. Ordering ID variable after proc transpose
    • Ordering ID variable after proc transpose (26 lines)
      From: J <jdiebal@GMAIL.COM>
    • Re: Ordering ID variable after proc transpose (47 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Ordering ID variable after proc transpose (49 lines)
      From: KP Singh <kpsingh4074@GMAIL.COM>
    • Re: Ordering ID variable after proc transpose (46 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Ordering ID variable after proc transpose (59 lines)
      From: JD <jdiebal@GMAIL.COM>
    • Re: Ordering ID variable after proc transpose (98 lines)
      From: KP Singh <kpsingh4074@GMAIL.COM>
    • Re: Ordering ID variable after proc transpose (106 lines)
      From: JD <jdiebal@GMAIL.COM>
    • Re: Ordering ID variable after proc transpose (161 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Ordering ID variable after proc transpose (181 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Ordering ID variable after proc transpose (202 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>
    • Re: Ordering ID variable after proc transpose (237 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Ordering ID variable after proc transpose (255 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: Ordering ID variable after proc transpose (296 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Ordering ID variable after proc transpose (314 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Ordering ID variable after proc transpose (262 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Ordering ID variable after proc transpose (277 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: Ordering ID variable after proc transpose (320 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Ordering ID variable after proc transpose (345 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: Ordering ID variable after proc transpose (294 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Ordering ID variable after proc transpose (300 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

24. Outputting Excel comments
    • Outputting Excel comments (18 lines)
      From: Randy Rosso <rossonova@GMAIL.COM>
    • Re: Outputting Excel comments (43 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: Outputting Excel comments (53 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>
    • Re: Outputting Excel comments (109 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Outputting Excel comments (32 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Outputting Excel comments (114 lines)
      From: Randy Rosso <rossonova@GMAIL.COM>
    • Re: Outputting Excel comments (10 lines)
      From: Randy Rosso <rossonova@GMAIL.COM>
    • Re: Outputting Excel comments (19 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Outputting Excel comments (54 lines)
      From: Randy Rosso <rossonova@GMAIL.COM>
    • Re: Outputting Excel comments (55 lines)
      From: Teed, Lionel <Lionel.Teed@TD.COM>
    • Re: Outputting Excel comments (64 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Outputting Excel comments (57 lines)
      From: Alan Churchill <savian.net@GMAIL.COM>

25. Program still running after getting all PDF reports.
    • Program still running after getting all PDF reports. (157 lines)
      From: SAS Analyst <analystprasad@YAHOO.CO.IN>

26. Proper way to clear output;?
    • Proper way to clear output;? (23 lines)
      From: Peter Timusk <petertimusk@PROGRAMDOCUMENTATION.COM>
    • Re: Proper way to clear output;? (31 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Proper way to clear output;? (37 lines)
      From: Fareeza Khurshed <fkhurshed@GMAIL.COM>
    • Re: Proper way to clear output;? (43 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: Proper way to clear output;? (49 lines)
      From: Peter Timusk <petertimusk@PROGRAMDOCUMENTATION.COM>
    • Re: Proper way to clear output;? (20 lines)
      From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM>
    • Re: Proper way to clear output;? (27 lines)
      From: Peter Timusk <petertimusk@PROGRAMDOCUMENTATION.COM>

27. Reading >255 columns of Excel XLSX file
    • Reading >255 columns of Excel XLSX file (15 lines)
      From: Ted Clay <tclay@ASHLANDHOME.NET>
    • Re: Reading >255 columns of Excel XLSX file (31 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Reading >255 columns of Excel XLSX file (19 lines)
      From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM>
    • Reading >255 columns of Excel XLSX file (43 lines)
      From: Ted Clay <tclay@ASHLANDHOME.NET>
    • Re: Reading >255 columns of Excel XLSX file (52 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Reading >255 columns of Excel XLSX file (24 lines)
      From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM>
    • Re: Reading >255 columns of Excel XLSX file (41 lines)
      From: Ted Clay <tclay@ASHLANDHOME.NET>
    • Re: Reading >255 columns of Excel XLSX file (49 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

28. Reminder: SGF Comes to Toronto
    • Reminder: SGF Comes to Toronto (66 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

29. Reordering variables
    • Reordering variables (34 lines)
      From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>
    • Re: Reordering variables (43 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Reordering variables (70 lines)
      From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>
    • Re: Reordering variables (78 lines)
      From: Fareeza Khurshed <fkhurshed@GMAIL.COM>
    • Re: Reordering variables (85 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Reordering variables (100 lines)
      From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>

30. SAS Help
    • SAS Help (24 lines)
      From: A K <aaykay.k@GMAIL.COM>
    • Re: SAS Help (47 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: SAS Help (32 lines)
      From: Bhupinder Singh Farmaha <bhupi80singh@YAHOO.CO.IN>
    • Re: SAS Help (52 lines)
      From: Dennis Fisher <Dennis.Fisher@CSULB.EDU>
    • Re: SAS Help (37 lines)
      From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM>
    • Re: SAS Help (55 lines)
      From: Teed, Lionel <Lionel.Teed@TD.COM>

31. SAS Users - Summer Conferences
    • SAS Users - Summer Conferences (9 lines)
      From: Tricia Aanderud <tricia.aanderud@AND-DATA.COM>

32. SAS and TIOBE
    • SAS and TIOBE (35 lines)
      From: Ben Powell <bpowell555@GMAIL.COM>
    • Re: SAS and TIOBE (7 lines)
      From: Ben Powell <bpowell555@GMAIL.COM>
    • Re: SAS and TIOBE (56 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: SAS and TIOBE (66 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: SAS and TIOBE (100 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

33. SQL set operator EXCEPT sorts data?
    • SQL set operator EXCEPT sorts data? (38 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: SQL set operator EXCEPT sorts data? (52 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: SQL set operator EXCEPT sorts data? (54 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: SQL set operator EXCEPT sorts data? (96 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
    • Re: SQL set operator EXCEPT sorts data? (82 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: SQL set operator EXCEPT sorts data? (121 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: SQL set operator EXCEPT sorts data? (98 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: SQL set operator EXCEPT sorts data? (121 lines)
      From: Fareeza Khurshed <fkhurshed@GMAIL.COM>
    • Re: SQL set operator EXCEPT sorts data? (136 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

34. Simple long to wide task
    • Simple long to wide task (27 lines)
      From: Zach Peery <mpeery@WISC.EDU>
    • Re: Simple long to wide task (43 lines)
      From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV>
    • Re: Simple long to wide task (71 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>
    • Re: Simple long to wide task (94 lines)
      From: Zach Peery <mpeery@WISC.EDU>
    • Re: Simple long to wide task (108 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Simple long to wide task (53 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Simple long to wide task (35 lines)
      From: Hongyan Lu <hongyanlu@YAHOO.COM>
    • Re: Simple long to wide task (109 lines)
      From: Ryan A. Leonard <ral@ALUMNI.UPENN.EDU>

35. What do if Fatal ODS error has occurred .
    • What do if Fatal ODS error has occurred . (24 lines)
      From: SAS Analyst <analystprasad@YAHOO.CO.IN>

36. When Two eqauls one....
    • When Two eqauls one.... (33 lines)
      From: Teed, Lionel <Lionel.Teed@TD.COM>
    • Re: When Two eqauls one.... (49 lines)
      From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV>

37. When will we get descriptive statistics out of SQL?
    • When will we get descriptive statistics out of SQL? (19 lines)
      From: Roland Berry <rolandberry@HOTMAIL.COM>

38. call symput causes error:Apparent symbolic reference not resolved
    • Re: call symput causes error:Apparent symbolic reference not resolved (87 lines)
      From: tony tony <tonysingsong@GMAIL.COM>

39. converting Proc sort + Datastep merge into Proc SQL joins
    • converting Proc sort + Datastep merge into Proc SQL joins (62 lines)
      From: Pradeep <chittiprolupradeep@GMAIL.COM>
    • Re: converting Proc sort + Datastep merge into Proc SQL joins (104 lines)
      From: Brandon Geise <bdgeise@GEISINGER.EDU>
    • Re: converting Proc sort + Datastep merge into Proc SQL joins (78 lines)
      From: Sigurd W. Hermansen <hermans1@WESTAT.COM>
    • Re: converting Proc sort + Datastep merge into Proc SQL joins (144 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: converting Proc sort + Datastep merge into Proc SQL joins (132 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: converting Proc sort + Datastep merge into Proc SQL joins (189 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

40. dataset name parsing macro - does it exist?
    • dataset name parsing macro - does it exist? (49 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: dataset name parsing macro - does it exist? (76 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: dataset name parsing macro - does it exist? (82 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

41. do not compute percent in proc freq out= data set
    • do not compute percent in proc freq out= data set (48 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

42. how to compare and verify results
    • how to compare and verify results (27 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: how to compare and verify results (37 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

43. how to hash-object this?
    • how to hash-object this? (51 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: how to hash-object this? (84 lines)
      From: Fried Egg <friedegg2012@GMAIL.COM>
    • Re: how to hash-object this? (93 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: how to hash-object this? (101 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: how to hash-object this? (111 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: how to hash-object this? (98 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: how to hash-object this? (148 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: how to hash-object this? (169 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: how to hash-object this? (206 lines)
      From: Fried Egg <friedegg2012@GMAIL.COM>
    • Re: how to hash-object this? (278 lines)
      From: Fried Egg <friedegg2012@GMAIL.COM>
    • Re: how to hash-object this? (290 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

44. interaction btw outer and inner queries
    • Re: interaction btw outer and inner queries (55 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
    • Re: interaction btw outer and inner queries (69 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: interaction btw outer and inner queries (66 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: interaction btw outer and inner queries (45 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: interaction btw outer and inner queries (62 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

45. no directory, a shortcomgin of SAS editor?
    • no directory, a shortcomgin of SAS editor? (19 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: no directory, a shortcomgin of SAS editor? (36 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: no directory, a shortcomgin of SAS editor? (53 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: no directory, a shortcomgin of SAS editor? (59 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: no directory, a shortcomgin of SAS editor? (36 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: no directory, a shortcomgin of SAS editor? (65 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

46. renaming data sets through loops
    • renaming data sets through loops (83 lines)
      From: tony tony <tonysingsong@GMAIL.COM>
    • Re: renaming data sets through loops (25 lines)
      From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM>
    • Re: renaming data sets through loops (44 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: renaming data sets through loops (54 lines)
      From: tony tony <tonysingsong@GMAIL.COM>
    • Re: renaming data sets through loops (49 lines)
      From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM>
    • Re: renaming data sets through loops (58 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: renaming data sets through loops (69 lines)
      From: Randy Herbison <RandyHerbison@WESTAT.COM>

47. reset the default program open folder
    • reset the default program open folder (16 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: reset the default program open folder (28 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: reset the default program open folder (46 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: reset the default program open folder (63 lines)
      From: KP Singh <kpsingh4074@GMAIL.COM>
    • Re: reset the default program open folder (66 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

48. selecting multiple samples within one shot
    • selecting multiple samples within one shot (17 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: selecting multiple samples within one shot (35 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: selecting multiple samples within one shot (66 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: selecting multiple samples within one shot (91 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: selecting multiple samples within one shot (117 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: selecting multiple samples within one shot (134 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: selecting multiple samples within one shot (44 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: selecting multiple samples within one shot (173 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: selecting multiple samples within one shot (176 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: selecting multiple samples within one shot (215 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: selecting multiple samples within one shot (65 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: selecting multiple samples within one shot (189 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: selecting multiple samples within one shot (209 lines)
      From: Fareeza Khurshed <fkhurshed@GMAIL.COM>
    • Re: selecting multiple samples within one shot (224 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: selecting multiple samples within one shot (44 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: selecting multiple samples within one shot (24 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>

49. survival analysis - help
    • survival analysis - help (18 lines)
      From: bigtime anuj <cool21.engg@GMAIL.COM>
    • Re: survival analysis - help (43 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: survival analysis - help (28 lines)
      From: Fareeza Khurshed <fkhurshed@GMAIL.COM>
    • Re: survival analysis - help (24 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: survival analysis - help (38 lines)
      From: Yuewei Liu <contact@YUEWEILIU.COM>