Table of contents:

• Analytics 2011 Conference - Oct 24-25, Orlando, Florida
• Automatic reply: SAS-L Digest - 15 Jul 2011 - Special issue (#2011-677)
• Automatic reply: SAS-L Digest - 21 Jul 2011 - Special issue (#2011-693)
• Autosvar: SAS-L Digest - 18 Jul 2011 - Special issue (#2011-683)
• Chance to Make SAS-L History: Did You Know That...
• Code review (3 messages)
• Comparison between datastep and proc SQL (5 messages)
• Dataflux vs DI studio (2 messages)
• Drill across with SAS BI tools
• ExcelXP embedded titles and footnotes (2 messages)
• ExcelXP row height weirdness (2 messages)
• FW: Transition to ICD-10 Code Sets
• Figuring out Age in Years, Months and Days (8 messages)
• Forcing "[variable] is uninitialized" to show up as an error (9 messages)
• How to identify groups of consecutive records? (5 messages)
• How to sort words in a string? (9 messages)
• Identifyiing groups
• Impossible to preload a hybrid format?
• Just a test... Do not respond. (2 messages)
• Kindling Your Desire for SAS 9.3 Documentation (4 messages)
• Likelihood ratio test using group statement in proc mixed (3 messages)
• Line too long in Editor? Error in Batch (3 messages)
• My code generating a random sample (2 messages)
• NLMIXED - Prob Estimate, Averaged Across Gender
• Negative Bionomial for non-count data ??
• Non-inferiority: three methods, three pigs, repeated measures
• ODS/pdf, Acrobat problem
• OT: QingDao
• OT: The introduction of modern arithmetic to the West in the 13th century
• PC SAS - identifying duplicate and overlapping dates (5 messages)
• PROC BOX PLOT (2 messages)
• PROC SURVEYFREQ SE versus SUDAAN (2 messages)
• Proc MI
• Proc logistic trap for unwary (6 messages)
• Proc report (4 messages)
• Proc report problem help (2 messages)
• Proc sort vs. Proc SQL; order by (6 messages)
• QingDao (2 messages)
• Record Linking (2 messages)
• SAS 9.3 notes (8 messages)
• SAS Universal Viewer 1.1
• SQL: Case
• Sample large datasets with observations logically removed (10 messages)
• Simple FREQ Question (& MEANS) (2 messages)
• Splitting Intake Records (2 messages)
• Statistics Classes: Online and Interactive
• The introduction of modern arithmetic to the West in the 13th century
• User asked for termination (Thanks)
• Warning Message About Collating Sequence When Downloading
• converting a decimal to character (6 messages)
• counting observation by groups (3 messages)
• create dynamic code
• how to solve this senario? (2 messages)
• multiple events on a single day calendar. (9 messages)
• need dynamic code (11 messages)
• need help to upgrade the code (3 messages)
• option for _webout in sas process (6 messages)
• proc mixed with nested random effect (3 messages)
• runsubmit.com disabled (2 messages)
• sas macro urgent help (3 messages)
• strange behavior of the Macro (8 messages)
• strange, subsetting IF statement inside a loop (7 messages)
• the "standard" code generating a sample (10 messages)
• transcoding warning while reading a flatfile in DI-Studio
• transpose? (3 messages)
• using #BYVAL (LABEL) with Line statement in Proc Report (9 messages)
• very interesting! set one two ..., what's make the difference? (15 messages)

1. Analytics 2011 Conference - Oct 24-25, Orlando, Florida
   • Analytics 2011 Conference - Oct 24-25, Orlando, Florida (17 lines)
     From: Vincent Granville <vincentg@DATASHAPING.COM>

2. Automatic reply: SAS-L Digest - 15 Jul 2011 - Special issue (#2011-677)
   • Automatic reply: SAS-L Digest - 15 Jul 2011 - Special issue (#2011-677) (22 lines)
     From: Carol Olson <Carol.Olson@MEREDITH.COM>

3. Automatic reply: SAS-L Digest - 21 Jul 2011 - Special issue (#2011-693)
   • Automatic reply: SAS-L Digest - 21 Jul 2011 - Special issue (#2011-693) (22 lines)
     From: Carol Olson <Carol.Olson@MEREDITH.COM>

4. Autosvar: SAS-L Digest - 18 Jul 2011 - Special issue (#2011-683)
   • Autosvar: SAS-L Digest - 18 Jul 2011 - Special issue (#2011-683) (12 lines)
     From: Tony Qureshi <Tony.Qureshi@KI.SE>

5. Chance to Make SAS-L History: Did You Know That...
   • Re: Chance to Make SAS-L History: Did You Know That... (16 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>

6. Code review
   • Code review (12 lines)
     From: polyphonic48@gmail.com <polyphonic48@GMAIL.COM>
   • Re: Code review (20 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: Code review (26 lines)
     From: polyphonic48@gmail.com <polyphonic48@GMAIL.COM>

7. Comparison between datastep and proc SQL
   • Comparison between datastep and proc SQL (23 lines)
     From: SAS_learner <proccontents@GMAIL.COM>
   • Re: Comparison between datastep and proc SQL (42 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: Comparison between datastep and proc SQL (36 lines)
     From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US>
   • Re: Comparison between datastep and proc SQL (32 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: Comparison between datastep and proc SQL (45 lines)
     From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

8. Dataflux vs DI studio
   • Dataflux vs DI studio (15 lines)
     From: Shanks N <shanks.n@GMAIL.COM>
   • Re: Dataflux vs DI studio (37 lines)
     From: Murphy Choy <goladin@GMAIL.COM>

9. Drill across with SAS BI tools
   • Drill across with SAS BI tools (19 lines)
     From: Sterling Paramore <gnilrets@GMAIL.COM>

10. ExcelXP embedded titles and footnotes
    • Re: ExcelXP embedded titles and footnotes (45 lines)
      From: Andre Wielki <wielki@INED.FR>
    • Re: ExcelXP embedded titles and footnotes (69 lines)
      From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>

11. ExcelXP row height weirdness
    • ExcelXP row height weirdness (49 lines)
      From: Richard Devenezia <rdevenezia@GMAIL.COM>
    • Re: ExcelXP row height weirdness (83 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>

12. FW: Transition to ICD-10 Code Sets
    • FW: Transition to ICD-10 Code Sets (34 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

13. Figuring out Age in Years, Months and Days
    • Figuring out Age in Years, Months and Days (35 lines)
      From: John Parker <John.V.Parker@KP.ORG>
    • Re: Figuring out Age in Years, Months and Days (48 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Figuring out Age in Years, Months and Days (61 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: Figuring out Age in Years, Months and Days (137 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>
    • Re: Figuring out Age in Years, Months and Days (106 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Figuring out Age in Years, Months and Days (138 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Figuring out Age in Years, Months and Days (154 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>
    • Re: Figuring out Age in Years, Months and Days (43 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>

14. Forcing "[variable] is uninitialized" to show up as an error
    • Forcing "[variable] is uninitialized" to show up as an error (19 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: Forcing "[variable] is uninitialized" to show up as an error (28 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Forcing "[variable] is uninitialized" to show up as an error (25 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Forcing "[variable] is uninitialized" to show up as an error (30 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Forcing "[variable] is uninitialized" to show up as an error (48 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: Forcing "[variable] is uninitialized" to show up as an error (24 lines)
      From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>
    • Re: Forcing "[variable] is uninitialized" to show up as an error (55 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Forcing "[variable] is uninitialized" to show up as an error (33 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Forcing "[variable] is uninitialized" to show up as an error (37 lines)
      From: John Hendrickx <john2.hendrickx@GMAIL.COM>

15. How to identify groups of consecutive records?
    • How to identify groups of consecutive records? (60 lines)
      From: Vladimir Grechko <vlad.grechko@MAIL.RU>
    • Re: How to identify groups of consecutive records? (107 lines)
      From: Paul Dorfman <sashole@BELLSOUTH.NET>
    • Re: How to identify groups of consecutive records? (95 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: How to identify groups of consecutive records? (114 lines)
      From: Paul Dorfman <sashole@BELLSOUTH.NET>
    • Re: How to identify groups of consecutive records? (134 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

16. How to sort words in a string?
    • How to sort words in a string? (13 lines)
      From: Steven Zhang <zzhang@HSPH.HARVARD.EDU>
    • Re: How to sort words in a string? (34 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: How to sort words in a string? (43 lines)
      From: Zibiao Zhang <zzhang@HSPH.HARVARD.EDU>
    • Re: How to sort words in a string? (25 lines)
      From: Vandenbroucke, David A <David.A.Vandenbroucke@HUD.GOV>
    • Re: How to sort words in a string? (45 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: How to sort words in a string? (15 lines)
      From: Byron Kirby <byronkirby@GMAIL.COM>
    • Re: How to sort words in a string? (12 lines)
      From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>
    • Re: How to sort words in a string? (43 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: How to sort words in a string? (55 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

17. Identifyiing groups
    • Identifyiing groups (44 lines)
      From: Randy <randistan69@HOTMAIL.COM>

18. Impossible to preload a hybrid format?
    • Impossible to preload a hybrid format? (24 lines)
      From: John Smith <js8765@GOOGLEMAIL.COM>

19. Just a test... Do not respond.
    • Just a test... Do not respond. (13 lines)
      From: Jordan, Lewis <Lewis.Jordan@WEYERHAEUSER.COM>
    • Re: Just a test... Do not respond. (18 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

20. Kindling Your Desire for SAS 9.3 Documentation
    • Kindling Your Desire for SAS 9.3 Documentation (52 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Kindling Your Desire for SAS 9.3 Documentation (55 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>
    • Re: Kindling Your Desire for SAS 9.3 Documentation (73 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Kindling Your Desire for SAS 9.3 Documentation (32 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

21. Likelihood ratio test using group statement in proc mixed
    • Likelihood ratio test using group statement in proc mixed (40 lines)
      From: Howard Rundle <hrundle@UOTTAWA.CA>
    • Re: Likelihood ratio test using group statement in proc mixed (71 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: Likelihood ratio test using group statement in proc mixed (17 lines)
      From: Howard Rundle <hrundle@UOTTAWA.CA>

22. Line too long in Editor? Error in Batch
    • Line too long in Editor? Error in Batch (39 lines)
      From: Fareeza Khurshed <fkhurshed@GMAIL.COM>
    • Re: Line too long in Editor? Error in Batch (55 lines)
      From: Fareeza Khurshed <fkhurshed@GMAIL.COM>
    • Re: Line too long in Editor? Error in Batch (68 lines)
      From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>

23. My code generating a random sample
    • My code generating a random sample (51 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: My code generating a random sample (73 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>

24. NLMIXED - Prob Estimate, Averaged Across Gender
    • NLMIXED - Prob Estimate, Averaged Across Gender (29 lines)
      From: R B <ryan.andrew.black@GMAIL.COM>

25. Negative Bionomial for non-count data ??
    • Negative Bionomial for non-count data ?? (51 lines)
      From: Mark Bilton <mark.bilton@UNI-TUEBINGEN.DE>

26. Non-inferiority: three methods, three pigs, repeated measures
    • Non-inferiority: three methods, three pigs, repeated measures (50 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>

27. ODS/pdf, Acrobat problem
    • ODS/pdf, Acrobat problem (24 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>

28. OT: QingDao
    • Re: OT: QingDao (62 lines)
      From: little boy <goodmood.cynic8@GMAIL.COM>

29. OT: The introduction of modern arithmetic to the West in the 13th century
    • OT: The introduction of modern arithmetic to the West in the 13th century (22 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

30. PC SAS - identifying duplicate and overlapping dates
    • PC SAS - identifying duplicate and overlapping dates (56 lines)
      From: Vivian Barber <vibooks@ATT.NET>
    • Re: PC SAS - identifying duplicate and overlapping dates (82 lines)
      From: Muhammad Sohail <sohailbme@GMAIL.COM>
    • Re: PC SAS - identifying duplicate and overlapping dates (31 lines)
      From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>
    • Re: PC SAS - identifying duplicate and overlapping dates (162 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: PC SAS - identifying duplicate and overlapping dates (72 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

31. PROC BOX PLOT
    • PROC BOX PLOT (31 lines)
      From: John Mike <sasslick@GMAIL.COM>
    • Re: PROC BOX PLOT (35 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>

32. PROC SURVEYFREQ SE versus SUDAAN
    • PROC SURVEYFREQ SE versus SUDAAN (54 lines)
      From: Marc Mooney UMN <moon0078@UMN.EDU>
    • Re: PROC SURVEYFREQ SE versus SUDAAN (59 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

33. Proc MI
    • Proc MI (26 lines)
      From: William Shakespeare <shakespeare_1040@HOTMAIL.COM>

34. Proc logistic trap for unwary
    • Proc logistic trap for unwary (10 lines)
      From: Richard <r.hockey@SPH.UQ.EDU.AU>
    • Re: Proc logistic trap for unwary (31 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Proc logistic trap for unwary (33 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Proc logistic trap for unwary (26 lines)
      From: David J Moriarty <djmoriarty@CSUPOMONA.EDU>
    • Re: Proc logistic trap for unwary (30 lines)
      From: Richard <r.hockey@SPH.UQ.EDU.AU>
    • Re: Proc logistic trap for unwary (56 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>

35. Proc report
    • Proc report (16 lines)
      From: John Mike <sasslick@GMAIL.COM>
    • Re: Proc report (36 lines)
      From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>
    • Re: Proc report (36 lines)
      From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>
    • Re: Proc report (26 lines)
      From: Fareeza Khurshed <fkhurshed@GMAIL.COM>

36. Proc report problem help
    • Proc report problem help (68 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: Proc report problem help (82 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>

37. Proc sort vs. Proc SQL; order by
    • Re: Proc sort vs. Proc SQL; order by (74 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Proc sort vs. Proc SQL; order by (86 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Proc sort vs. Proc SQL; order by (132 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Proc sort vs. Proc SQL; order by (143 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Proc sort vs. Proc SQL; order by (14 lines)
      From: Byron Kirby <byronkirby@GMAIL.COM>
    • Re: Proc sort vs. Proc SQL; order by (32 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

38. QingDao
    • Re: QingDao (27 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: QingDao (43 lines)
      From: Murphy Choy <goladin@GMAIL.COM>

39. Record Linking
    • Record Linking (56 lines)
      From: Akshaya <akshaya.nathilvar@GMAIL.COM>
    • Re: Record Linking (75 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

40. SAS 9.3 notes
    • Re: SAS 9.3 notes (41 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: SAS 9.3 notes (53 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: SAS 9.3 notes (69 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: SAS 9.3 notes (87 lines)
      From: DUELL, BOB (ATTCINW) <bd9439@ATT.COM>
    • Re: SAS 9.3 notes (139 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: SAS 9.3 notes (84 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: SAS 9.3 notes (100 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: SAS 9.3 notes (32 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

41. SAS Universal Viewer 1.1
    • SAS Universal Viewer 1.1 (17 lines)
      From: Jordan, Lewis <Lewis.Jordan@WEYERHAEUSER.COM>

42. SQL: Case
    • SQL: Case (69 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>

43. Sample large datasets with observations logically removed
    • Sample large datasets with observations logically removed (53 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Sample large datasets with observations logically removed (67 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: Sample large datasets with observations logically removed (91 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: Sample large datasets with observations logically removed (96 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Sample large datasets with observations logically removed (109 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Sample large datasets with observations logically removed (83 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Sample large datasets with observations logically removed (90 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Sample large datasets with observations logically removed (101 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Re: Sample large datasets with observations logically removed (116 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Sample large datasets with observations logically removed (227 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>

44. Simple FREQ Question (& MEANS)
    • Simple FREQ Question (& MEANS) (61 lines)
      From: Daniel Yanosky <dyanosky@KENNESAW.EDU>
    • Re: Simple FREQ Question (& MEANS) (143 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>

45. Splitting Intake Records
    • Splitting Intake Records (51 lines)
      From: Bruce Johnson <chimanbjsas@GMAIL.COM>
    • Re: Splitting Intake Records (84 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

46. Statistics Classes: Online and Interactive
    • Statistics Classes: Online and Interactive (103 lines)
      From: Dorothy Middleton <courses@STATCOURSE.COM>

47. The introduction of modern arithmetic to the West in the 13th century
    • Re: The introduction of modern arithmetic to the West in the 13th century (35 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

48. User asked for termination (Thanks)
    • Re: User asked for termination (Thanks) (74 lines)
      From: Viraj Kumbhakarna <yourviraj@YAHOO.COM>

49. Warning Message About Collating Sequence When Downloading
    • Warning Message About Collating Sequence When Downloading (130 lines)
      From: Jack Clark <jclark@HILLTOP.UMBC.EDU>

50. converting a decimal to character
    • converting a decimal to character (29 lines)
      From: Christine Peloquin <christinepeloquin1@GMAIL.COM>
    • Re: converting a decimal to character (57 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: converting a decimal to character (51 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: converting a decimal to character (69 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: converting a decimal to character (96 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: converting a decimal to character (94 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

51. counting observation by groups
    • counting observation by groups (19 lines)
      From: Nuria Chapinal <nchapinal@YAHOO.COM>
    • Re: counting observation by groups (34 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: counting observation by groups (64 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

52. create dynamic code
    • create dynamic code (48 lines)
      From: SUBSCRIBE SAS-L Anonymous <sagar.s@SATVIKINC.COM>

53. how to solve this senario?
    • how to solve this senario? (32 lines)
      From: Nway <hymadsk@GMAIL.COM>
    • Re: how to solve this senario? (76 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>

54. multiple events on a single day calendar.
    • multiple events on a single day calendar. (18 lines)
      From: Steven Zhang <zzhang@HSPH.HARVARD.EDU>
    • multiple events on a single day calendar. (14 lines)
      From: Steven Zhang <zzhang@HSPH.HARVARD.EDU>
    • Re: multiple events on a single day calendar. (41 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: multiple events on a single day calendar. (34 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: multiple events on a single day calendar. (64 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: multiple events on a single day calendar. (104 lines)
      From: Zibiao Zhang <zzhang@HSPH.HARVARD.EDU>
    • Re: multiple events on a single day calendar. (130 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: multiple events on a single day calendar. (157 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: multiple events on a single day calendar. (138 lines)
      From: Zibiao Zhang <zzhang@HSPH.HARVARD.EDU>

55. need dynamic code
    • need dynamic code (64 lines)
      From: SUBSCRIBE SAS-L Anonymous <sagar.s@SATVIKINC.COM>
    • Re: need dynamic code (132 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: need dynamic code (9 lines)
      From: SUBSCRIBE SAS-L Anonymous <sagar.s@SATVIKINC.COM>
    • Re: need dynamic code (36 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: need dynamic code (175 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: need dynamic code (204 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: need dynamic code (27 lines)
      From: SUBSCRIBE SAS-L sagar <sagar.s@SATVIKINC.COM>
    • Re: need dynamic code (41 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: need dynamic code (20 lines)
      From: SUBSCRIBE SAS-L sagar <sagar.s@SATVIKINC.COM>
    • Re: need dynamic code (66 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: need dynamic code (77 lines)
      From: SUBSCRIBE SAS-L sagar <sagar.s@SATVIKINC.COM>

56. need help to upgrade the code
    • need help to upgrade the code (44 lines)
      From: "SUBSCRIBE SAS-L sagar". <sagar.s@SATVIKINC.COM>
    • Re: need help to upgrade the code (85 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: need help to upgrade the code (67 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>

57. option for _webout in sas process
    • option for _webout in sas process (14 lines)
      From: SUBSCRIBE SAS-L sagar <sagar.s@SATVIKINC.COM>
    • Re: option for _webout in sas process (29 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: option for _webout in sas process (45 lines)
      From: SUBSCRIBE SAS-L sagar <sagar.s@SATVIKINC.COM>
    • Re: option for _webout in sas process (79 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: option for _webout in sas process (41 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: option for _webout in sas process (131 lines)
      From: Chris Brooks <Chris.Brooks@ONS.GOV.UK>

58. proc mixed with nested random effect
    • proc mixed with nested random effect (39 lines)
      From: Carole Lunney <calunney@GMAIL.COM>
    • Re: proc mixed with nested random effect (61 lines)
      From: Robin R High <rhigh@UNMC.EDU>
    • Re: proc mixed with nested random effect (44 lines)
      From: Carole Lunney <calunney@GMAIL.COM>

59. runsubmit.com disabled
    • runsubmit.com disabled (7 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: runsubmit.com disabled (25 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

60. sas macro urgent help
    • sas macro urgent help (146 lines)
      From: SUBSCRIBE SAS-L Anonymous <sagar.s@SATVIKINC.COM>
    • Re: sas macro urgent help (164 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: sas macro urgent help (43 lines)
      From: SUBSCRIBE SAS-L Anonymous <sagar.s@SATVIKINC.COM>

61. strange behavior of the Macro
    • strange behavior of the Macro (141 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: strange behavior of the Macro (147 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: strange behavior of the Macro (161 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: strange behavior of the Macro (177 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: strange behavior of the Macro (185 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: strange behavior of the Macro (213 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: strange behavior of the Macro (26 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: strange behavior of the Macro (39 lines)
      From: SAS_learner <proccontents@GMAIL.COM>

62. strange, subsetting IF statement inside a loop
    • strange, subsetting IF statement inside a loop (46 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: strange, subsetting IF statement inside a loop (55 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: strange, subsetting IF statement inside a loop (105 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
    • Re: strange, subsetting IF statement inside a loop (77 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: strange, subsetting IF statement inside a loop (104 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: strange, subsetting IF statement inside a loop (135 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
    • Re: strange, subsetting IF statement inside a loop (43 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

63. the "standard" code generating a sample
    • the "standard" code generating a sample (46 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: the "standard" code generating a sample (64 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: the "standard" code generating a sample (90 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>
    • Re: the "standard" code generating a sample (77 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>
    • Re: the "standard" code generating a sample (44 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Re: the "standard" code generating a sample (103 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Re: the "standard" code generating a sample (151 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: the "standard" code generating a sample (168 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: the "standard" code generating a sample (38 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Re: the "standard" code generating a sample (80 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

64. transcoding warning while reading a flatfile in DI-Studio
    • Re: transcoding warning while reading a flatfile in DI-Studio (169 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

65. transpose?
    • transpose? (63 lines)
      From: Adriano Rodrigues <adriano@GPP.COM.BR>
    • Re: transpose? (123 lines)
      From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>
    • Re: transpose? (99 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

66. using #BYVAL (LABEL) with Line statement in Proc Report
    • using #BYVAL (LABEL) with Line statement in Proc Report (87 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: using #BYVAL (LABEL) with Line statement in Proc Report (12 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: using #BYVAL (LABEL) with Line statement in Proc Report (28 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: using #BYVAL (LABEL) with Line statement in Proc Report (45 lines)
      From: shyamprasad samisetti <shyam.cbz@GMAIL.COM>
    • Re: using #BYVAL (LABEL) with Line statement in Proc Report (103 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: using #BYVAL (LABEL) with Line statement in Proc Report (47 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: using #BYVAL (LABEL) with Line statement in Proc Report (147 lines)
      From: shyamprasad samisetti <shyam.cbz@GMAIL.COM>
    • Re: using #BYVAL (LABEL) with Line statement in Proc Report (47 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: using #BYVAL (LABEL) with Line statement in Proc Report (64 lines)
      From: SAS_learner <proccontents@GMAIL.COM>

67. very interesting! set one two ..., what's make the difference?
    • very interesting! set one two ..., what's make the difference? (52 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: very interesting! set one two ..., what's make the difference? (71 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: very interesting! set one two ..., what's make the difference? (92 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: very interesting! set one two ..., what's make the difference? (37 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: very interesting! set one two ..., what's make the difference? (59 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: very interesting! set one two ..., what's make the difference? (64 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: very interesting! set one two ..., what's make the difference? (55 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: very interesting! set one two ..., what's make the difference? (86 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: very interesting! set one two ..., what's make the difference? (80 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: very interesting! set one two ..., what's make the difference? (169 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: very interesting! set one two ..., what's make the difference? (193 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: very interesting! set one two ..., what's make the difference? (81 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: very interesting! set one two ..., what's make the difference? (52 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: very interesting! set one two ..., what's make the difference? (58 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: very interesting! set one two ..., what's make the difference? (147 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>