Table of contents:

• %nrquote issue with arrays
• AW: deviance in genmod (2 messages)
• Am I missing something easy? (4 messages)
• Automatic reply: SAS-L Digest - 22 Dec 2010 to 23 Dec 2010 (#2010-1367)
• Bus Error - core dumped (4 messages)
• Collapsing date records with no gaps (9 messages)
• Compare risk adjusted mortality rates (4 messages)
• Convert DATETIME19. to MMDDYY10. (2 messages)
• GUI interface for SAS code (10 messages)
• How to accunt for retroactivity in enrollment data (22 messages)
• IBNR / Chain Ladder
• IOM Bridge Object Spawner config
• Identify multiple births (6 messages)
• Installing SAS 64 bits (2 messages)
• Is there an easier way to solve this? (51 messages)
• Logistic Regression with Nested Data
• Macro variable referencing (10 messages)
• Multiple Titles inside Proc IML
• Newbie with SAS (4 messages)
• OT: Friday Humor
• PROC SORT Question (3 messages)
• PROC SQL - Multiple Statments (2 messages)
• PROC SQL Group by formatted values (4 messages)
• Proc NLMIXED "r-squared-like statistic for nonlinear model"
• RES: PROC SORT Question (3 messages)
• RES: PROC SQL - Multiple Statments
• RES: PROC SQL - Multiple Statments - Error (2 messages)
• RES: PROC SQL - Multiple Statments - Error(x2)
• RES: RES: PROC SORT Question (2 messages)
• RES: RES: PROC SQL - Multiple Statments - Error (2 messages)
• Raw import - Can SAS just ignore funky values?
• SAS Institute brings 100 jobs to Cary
• SAS phreg question (3 messages)
• Sampling Error & Poisson Dist (2 messages)
• Stored Process execution question (answer)
• The Post From SAS-L
• Timing SAS runs (7 messages)
• cluster bar chart with +/- 1 standard error (4 messages)
• deviance in genmod (3 messages)
• how to flag condition as 20 <diff<100 (8 messages)
• how to solve this senario? (5 messages)
• last.id=1 or 0, how SAS supervisor knows about it? (3 messages)
• merge within 30 days by id (4 messages)
• send several attachment in a mail (3 messages)
• the time for the printed output

1. %nrquote issue with arrays
   • Re: %nrquote issue with arrays (46 lines)
     From: Allen Ziegenfus <aziegenfus@GMAIL.COM>

2. AW: deviance in genmod
   • AW: deviance in genmod (101 lines)
     From: Gerstner, Doris Dipl.-Kffr. , MPH <Doris.Gerstner@MED.UNI-MUENCHEN.DE>
   • Re: AW: deviance in genmod (152 lines)
     From: Dale McLerran <stringplayer_2@YAHOO.COM>

3. Am I missing something easy?
   • Am I missing something easy? (133 lines)
     From: Long, Stuart (NIH/NIEHS) [C] <long3@NIEHS.NIH.GOV>
   • Re: Am I missing something easy? (146 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Am I missing something easy? (162 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Am I missing something easy? (208 lines)
     From: Long, Stuart (NIH/NIEHS) [C] <long3@NIEHS.NIH.GOV>

4. Automatic reply: SAS-L Digest - 22 Dec 2010 to 23 Dec 2010 (#2010-1367)
   • Automatic reply: SAS-L Digest - 22 Dec 2010 to 23 Dec 2010 (#2010-1367) (16 lines)
     From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU>

5. Bus Error - core dumped
   • Bus Error - core dumped (35 lines)
     From: LEI ZICHAO <leizichao@ALUMNI.NUS.EDU.SG>
   • Re: Bus Error - core dumped (60 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: Bus Error - core dumped (97 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Re: Bus Error - core dumped (114 lines)
     From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

6. Collapsing date records with no gaps
   • Re: Collapsing date records with no gaps (153 lines)
     From: Jerry <i89rt5@GMAIL.COM>
   • Re: Collapsing date records with no gaps (168 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Collapsing date records with no gaps (232 lines)
     From: Jerry <i89rt5@GMAIL.COM>
   • Re: Collapsing date records with no gaps (250 lines)
     From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
   • Re: Collapsing date records with no gaps (261 lines)
     From: Jerry <i89rt5@GMAIL.COM>
   • Re: Collapsing date records with no gaps (351 lines)
     From: Jerry <i89rt5@GMAIL.COM>
   • Re: Collapsing date records with no gaps (180 lines)
     From: Daniel Nordlund <djnordlund@FRONTIER.COM>
   • Re: Collapsing date records with no gaps (382 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Collapsing date records with no gaps (503 lines)
     From: Jerry <i89rt5@GMAIL.COM>

7. Compare risk adjusted mortality rates
   • Compare risk adjusted mortality rates (44 lines)
     From: Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>
   • Re: Compare risk adjusted mortality rates (73 lines)
     From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU>
   • Re: Compare risk adjusted mortality rates (90 lines)
     From: Mike Zdeb <msz03@ALBANY.EDU>
   • Re: Compare risk adjusted mortality rates (134 lines)
     From: Robin R High <rhigh@UNMC.EDU>

8. Convert DATETIME19. to MMDDYY10.
   • Convert DATETIME19. to MMDDYY10. (23 lines)
     From: Amy Krueger <amyk4422@GMAIL.COM>
   • Re: Convert DATETIME19. to MMDDYY10. (43 lines)
     From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

9. GUI interface for SAS code
   • GUI interface for SAS code (15 lines)
     From: Vijayan Sundaram <vijchid@GMAIL.COM>
   • Re: GUI interface for SAS code (32 lines)
     From: goladin@gmail.com <goladin@GMAIL.COM>
   • Re: GUI interface for SAS code (29 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: GUI interface for SAS code (44 lines)
     From: goladin@gmail.com <goladin@GMAIL.COM>
   • Re: GUI interface for SAS code (58 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: GUI interface for SAS code (73 lines)
     From: goladin@gmail.com <goladin@GMAIL.COM>
   • Re: GUI interface for SAS code (49 lines)
     From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU>
   • Re: GUI interface for SAS code (89 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: GUI interface for SAS code (45 lines)
     From: Alan Churchill <alan.churchill@SAVIAN.NET>
   • Re: GUI interface for SAS code (101 lines)
     From: Nat Wooding <nathani@VERIZON.NET>

10. How to accunt for retroactivity in enrollment data
    • How to accunt for retroactivity in enrollment data (70 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (101 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (202 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (146 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: How to accunt for retroactivity in enrollment data (121 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: How to accunt for retroactivity in enrollment data (179 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (217 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (273 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (286 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (395 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (156 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (183 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: How to accunt for retroactivity in enrollment data (183 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Re: How to accunt for retroactivity in enrollment data (200 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: How to accunt for retroactivity in enrollment data (253 lines)
      From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (348 lines)
      From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (361 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (211 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (237 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: How to accunt for retroactivity in enrollment data (230 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (211 lines)
      From: Jerry <i89rt5@GMAIL.COM>
    • Re: How to accunt for retroactivity in enrollment data (486 lines)
      From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>

11. IBNR / Chain Ladder
    • Re: IBNR / Chain Ladder (42 lines)
      From: art297 <atabachneck@GMAIL.COM>

12. IOM Bridge Object Spawner config
    • IOM Bridge Object Spawner config (91 lines)
      From: Andy Bolton <AndrewBolton@HALIFAX.CO.UK>

13. Identify multiple births
    • Re: Identify multiple births (112 lines)
      From: Chua Lily <chloegal04@GMAIL.COM>
    • Re: Identify multiple births (208 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Identify multiple births (128 lines)
      From: Chua Lily <chloegal04@GMAIL.COM>
    • Re: Identify multiple births (152 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Identify multiple births (152 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Identify multiple births (177 lines)
      From: Murphy Choy <goladin@GMAIL.COM>

14. Installing SAS 64 bits
    • Re: Installing SAS 64 bits (30 lines)
      From: art297 <atabachneck@GMAIL.COM>
    • Re: Installing SAS 64 bits (40 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

15. Is there an easier way to solve this?
    • Is there an easier way to solve this? (35 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (77 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Is there an easier way to solve this? (90 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Is there an easier way to solve this? (99 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (170 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Is there an easier way to solve this? (190 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Is there an easier way to solve this? (222 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (244 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Is there an easier way to solve this? (256 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (255 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (66 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Is there an easier way to solve this? (78 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Is there an easier way to solve this? (374 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Is there an easier way to solve this? (61 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: Is there an easier way to solve this? (79 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Is there an easier way to solve this? (98 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (161 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Is there an easier way to solve this? (177 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (191 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (204 lines)
      From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>
    • Re: Is there an easier way to solve this? (226 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Is there an easier way to solve this? (227 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (264 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Is there an easier way to solve this? (277 lines)
      From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>
    • Re: Is there an easier way to solve this? (293 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Is there an easier way to solve this? (293 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Is there an easier way to solve this? (326 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (316 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Is there an easier way to solve this? (378 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Is there an easier way to solve this? (23 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Is there an easier way to solve this? (401 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Is there an easier way to solve this? (339 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Is there an easier way to solve this? (419 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Is there an easier way to solve this? (35 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (382 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Is there an easier way to solve this? (444 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (461 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Is there an easier way to solve this? (17 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (503 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Is there an easier way to solve this? (472 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: Is there an easier way to solve this? (506 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (601 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Is there an easier way to solve this? (627 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (722 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Is there an easier way to solve this? (30 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (48 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Is there an easier way to solve this? (57 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Is there an easier way to solve this? (657 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Is there an easier way to solve this? (792 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Is there an easier way to solve this? (64 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Is there an easier way to solve this? (78 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

16. Logistic Regression with Nested Data
    • Logistic Regression with Nested Data (75 lines)
      From: Paul Miller <pjmiller_57@YAHOO.COM>

17. Macro variable referencing
    • Re: Macro variable referencing (216 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: Macro variable referencing (295 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Macro variable referencing (310 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: Macro variable referencing (325 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: Macro variable referencing (83 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Macro variable referencing (96 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Macro variable referencing (102 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Macro variable referencing (113 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Macro variable referencing (169 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Macro variable referencing (137 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

18. Multiple Titles inside Proc IML
    • Re: Multiple Titles inside Proc IML (21 lines)
      From: art297 <atabachneck@GMAIL.COM>

19. Newbie with SAS
    • Re: Newbie with SAS (41 lines)
      From: art297 <atabachneck@GMAIL.COM>
    • Re: Newbie with SAS (53 lines)
      From: Allen Ziegenfus <aziegenfus@GMAIL.COM>
    • Re: Newbie with SAS (63 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Newbie with SAS (21 lines)
      From: art297 <atabachneck@GMAIL.COM>

20. OT: Friday Humor
    • Re: OT: Friday Humor (47 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

21. PROC SORT Question
    • PROC SORT Question (98 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>
    • Re: PROC SORT Question (117 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: PROC SORT Question (106 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

22. PROC SQL - Multiple Statments
    • PROC SQL - Multiple Statments (55 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>
    • Re: PROC SQL - Multiple Statments (96 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

23. PROC SQL Group by formatted values
    • PROC SQL Group by formatted values (39 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: PROC SQL Group by formatted values (59 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: PROC SQL Group by formatted values (94 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: PROC SQL Group by formatted values (113 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>

24. Proc NLMIXED "r-squared-like statistic for nonlinear model"
    • Proc NLMIXED "r-squared-like statistic for nonlinear model" (57 lines)
      From: Phil Townsend <ptownsend@WISC.EDU>

25. RES: PROC SORT Question
    • RES: PROC SORT Question (138 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>
    • RES: PROC SORT Question (120 lines)
      From: =?utf-8?B?UmljYXJkbyBHb27Dp2FsdmVzIGRhIFNpbHZh?= <rgs.rsilva@BANCOVOTORANTIM.COM.BR>
    • Re: RES: PROC SORT Question (155 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

26. RES: PROC SQL - Multiple Statments
    • RES: PROC SQL - Multiple Statments (111 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>

27. RES: PROC SQL - Multiple Statments - Error
    • RES: PROC SQL - Multiple Statments - Error (163 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>
    • Re: RES: PROC SQL - Multiple Statments - Error (177 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

28. RES: PROC SQL - Multiple Statments - Error(x2)
    • Re: RES: PROC SQL - Multiple Statments - Error(x2) (220 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

29. RES: RES: PROC SORT Question
    • RES: RES: PROC SORT Question (207 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>
    • Re: RES: RES: PROC SORT Question (259 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

30. RES: RES: PROC SQL - Multiple Statments - Error
    • RES: RES: PROC SQL - Multiple Statments - Error (211 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>
    • Re: RES: RES: PROC SQL - Multiple Statments - Error (254 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

31. Raw import - Can SAS just ignore funky values?
    • Re: Raw import - Can SAS just ignore funky values? (46 lines)
      From: art297 <atabachneck@GMAIL.COM>

32. SAS Institute brings 100 jobs to Cary
    • SAS Institute brings 100 jobs to Cary (11 lines)
      From: Vincent Granville <vincentg@DATASHAPING.COM>

33. SAS phreg question
    • Re: SAS phreg question (88 lines)
      From: Lang Chen <Lang.Chen@CCC.UAB.EDU>
    • Re: SAS phreg question (141 lines)
      From: Robin R High <rhigh@UNMC.EDU>
    • Re: SAS phreg question (163 lines)
      From: Lang Chen <Lang.Chen@CCC.UAB.EDU>

34. Sampling Error & Poisson Dist
    • Sampling Error & Poisson Dist (14 lines)
      From: Lynn <lgoetz_10@HOTMAIL.COM>
    • Re: Sampling Error & Poisson Dist (35 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

35. Stored Process execution question (answer)
    • Re: Stored Process execution question (answer) (214 lines)
      From: Allen Ziegenfus <aziegenfus@GMAIL.COM>

36. The Post From SAS-L
    • The Post From SAS-L (93 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

37. Timing SAS runs
    • Re: Timing SAS runs (41 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Timing SAS runs (57 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Timing SAS runs (50 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Timing SAS runs (48 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Timing SAS runs (75 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Timing SAS runs (36 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Timing SAS runs (108 lines)
      From: Clapson, Andrew - PPD/DPP <Andrew.Clapson@STATCAN.GC.CA>

38. cluster bar chart with +/- 1 standard error
    • cluster bar chart with +/- 1 standard error (106 lines)
      From: Ali Zanaty <zanaty2005@YAHOO.COM>
    • Re: cluster bar chart with +/- 1 standard error (160 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: cluster bar chart with +/- 1 standard error (53 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: cluster bar chart with +/- 1 standard error (274 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

39. deviance in genmod
    • deviance in genmod (30 lines)
      From: Doris Gerstner <doris.gerstner@MED.UNI-MUENCHEN.DE>
    • Re: deviance in genmod (86 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: deviance in genmod (123 lines)
      From: Robin R High <rhigh@UNMC.EDU>

40. how to flag condition as 20 <diff<100
    • Re: how to flag condition as 20 <diff<100 (65 lines)
      From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
    • Re: how to flag condition as 20 <diff<100 (91 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: how to flag condition as 20 <diff<100 (115 lines)
      From: vaibhav wadhera <vaibhavwadhera@GMAIL.COM>
    • Re: how to flag condition as 20 <diff<100 (127 lines)
      From: Jeff <zhujp98@GMAIL.COM>
    • Re: how to flag condition as 20 <diff<100 (135 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: how to flag condition as 20 <diff<100 (161 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: how to flag condition as 20 <diff<100 (190 lines)
      From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
    • Re: how to flag condition as 20 <diff<100 (242 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

41. how to solve this senario?
    • how to solve this senario? (66 lines)
      From: Nway <hymadsk@GMAIL.COM>
    • Re: how to solve this senario? (80 lines)
      From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
    • Re: how to solve this senario? (83 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: how to solve this senario? (82 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: how to solve this senario? (96 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

42. last.id=1 or 0, how SAS supervisor knows about it?
    • last.id=1 or 0, how SAS supervisor knows about it? (49 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: last.id=1 or 0, how SAS supervisor knows about it? (57 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: last.id=1 or 0, how SAS supervisor knows about it? (87 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

43. merge within 30 days by id
    • merge within 30 days by id (52 lines)
      From: Kim Brown <kibrown@LADHS.ORG>
    • Re: merge within 30 days by id (79 lines)
      From: Mike Zdeb <msz03@ALBANY.EDU>
    • Re: merge within 30 days by id (7 lines)
      From: Kim Brown <kibrown@LADHS.ORG>
    • Re: merge within 30 days by id (68 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>

44. send several attachment in a mail
    • Re: send several attachment in a mail (48 lines)
      From: art297 <atabachneck@GMAIL.COM>
    • Re: send several attachment in a mail (76 lines)
      From: Ken Borowiak <evilpettingzoo97@AOL.COM>
    • Re: send several attachment in a mail (39 lines)
      From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM>

45. the time for the printed output
    • Re: the time for the printed output (58 lines)
      From: John Chapman <john.chapman@VIRGINBROADBAND.COM.AU>