Table of contents:

• & and the delimiter (2 messages)
• Any clever way to find if a char field contains anything that isn't a number? (3 messages)
• Automatic reply: Test for measuring trend
• COMMA. (2 messages)
• Content-type: text/html (4 messages)
• Convert data view to data set (6 messages)
• Converting Narrow Data Set to Wide Data Set (6 messages)
• Counting Max Trails using Level by ID (4 messages)
• DSD and the ending missing values (3 messages)
• Directly reference dataset created view lost the reference? (4 messages)
• FW: Internet2 Connection Established
• Framington Score
• Fwd: Much Faster Bootstraps Using SAS? -- Yes, the fastest to date... (3 messages)
• Fwd: Resolving macro variable in macroname
• Fwd: proc sql
• Hash vs OBS= (How to make a tie, not a winner) (4 messages)
• How to read this instream/raw data (2 messages)
• I got it RE: identify starting and ending column numbers
• ICD9 CM Removing large blocks text (3 messages)
• Importing .xlsx files with worksheet names >29 characters (2 messages)
• Incorporating a Baseline Hazard for a Binomial Logit
• Input reading beyond specified length. (7 messages)
• Job opening (NYC)
• NLMIXED Output combinations (2 messages)
• NLMIXED and GLIMMIX -Beta distribution
• New Computer
• Nonlinear optimization
• OT: Thursday Theory (2 messages)
• PRINT fileref in the FILE statement? (5 messages)
• Parsing regular table (3 messages)
• Proc Freq Horiz and Verticle lines
• Proc SQL left join speed being affected significantly by option (rename=)? (5 messages)
• Q: new computer (2 messages)
• RES: understanding spatial autocorrelation
• Resolving macro variable in macroname (8 messages)
• SAS code for calculating Framingham Risk Score (2 messages)
• SAS time (6 messages)
• Test for measuring trend (3 messages)
• Use symput to make a macro var (6 messages)
• Using value of a macro variable into another macro? (6 messages)
• X and Y in ODS REGION statement (PDF destination)
• [Poll] Your analytic career: how do you see yourself at 55? (4 messages)
• appropriate regression model for 12 level categorical response variable?
• change macro variable name dymacro? (5 messages)
• class statement in Proc PRINT (5 messages)
• coefficients for random effects (2 messages)
• data merging question (7 messages)
• dollar9. and comma9. (3 messages)
• duplicates emails from SAS-L (10 messages)
• equivalent of an offset in proc mixed (5 messages)
• file shortcuts question remade (2 messages)
• formatted input vs column input
• funny code, formatted input or list input or neither (2 messages)
• how to convert one variable into multiple columns according its value? (2 messages)
• how to get macro variable length (4 messages)
• identify starting and ending column numbers (11 messages)
• input statement vs. put statement (2 messages)
• length of numeric variables (12 messages)
• new computer (3 messages)
• output, loop, PDV (3 messages)
• proc report (3 messages)
• proc sql (6 messages)
• random functions (3 messages)
• reminder: EG v4.1 dies on Dec 1, 2010
• the d value of an informat, as in w.d or comma9.d (4 messages)
• variable-length records (3 messages)
• versions of SAS 9.2 (4 messages)

1. & and the delimiter
   • Re: & and the delimiter (52 lines)
     From: Pratap Kunwar <pkunwar@GMAIL.COM>
   • & and the delimiter (37 lines)
     From: bbser2009 <bbser2009@GMAIL.COM>

2. Any clever way to find if a char field contains anything that isn't a number?
   • Re: Any clever way to find if a char field contains anything that isn't a number? (89 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: Any clever way to find if a char field contains anything that isn't a number? (52 lines)
     From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
   • Re: Any clever way to find if a char field contains anything that isn't a number? (47 lines)
     From: Hoyle, Larry <larryhoyle@KU.EDU>

3. Automatic reply: Test for measuring trend
   • Automatic reply: Test for measuring trend (11 lines)
     From: Jill Ackerman <Jill.Ackerman@SAS.COM>

4. COMMA.
   • Re: COMMA. (41 lines)
     From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
   • COMMA. (34 lines)
     From: bbser2009 <bbser2009@GMAIL.COM>

5. Content-type: text/html
   • Re: Content-type: text/html (98 lines)
     From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
   • Re: Content-type: text/html (80 lines)
     From: Tolbert, William <tolbert.w@GHC.ORG>
   • Re: Content-type: text/html (50 lines)
     From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
   • Content-type: text/html (40 lines)
     From: Terjeson, Mark <Mterjeson@RUSSELL.COM>

6. Convert data view to data set
   • Re: Convert data view to data set (58 lines)
     From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
   • Re: Convert data view to data set (78 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: Convert data view to data set (66 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: Convert data view to data set (44 lines)
     From: js8765 <js8765@GOOGLEMAIL.COM>
   • Re: Convert data view to data set (31 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Convert data view to data set (21 lines)
     From: js8765 <js8765@GOOGLEMAIL.COM>

7. Converting Narrow Data Set to Wide Data Set
   • Re: Converting Narrow Data Set to Wide Data Set (160 lines)
     From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU>
   • Re: Converting Narrow Data Set to Wide Data Set (104 lines)
     From: Ian Whitlock <iw1sas@GMAIL.COM>
   • Re: Converting Narrow Data Set to Wide Data Set (129 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Converting Narrow Data Set to Wide Data Set (110 lines)
     From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU>
   • Re: Converting Narrow Data Set to Wide Data Set (85 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Converting Narrow Data Set to Wide Data Set (65 lines)
     From: Sally Muller <sallymuller@BELLSOUTH.NET>

8. Counting Max Trails using Level by ID
   • Re: Counting Max Trails using Level by ID (307 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: Counting Max Trails using Level by ID (257 lines)
     From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
   • Re: Counting Max Trails using Level by ID (149 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Counting Max Trails using Level by ID (109 lines)
     From: Craig Johnson <cjohns38@GMAIL.COM>

9. DSD and the ending missing values
   • Re: DSD and the ending missing values (29 lines)
     From: Nat Wooding <nathani@VERIZON.NET>
   • Re: DSD and the ending missing values (13 lines)
     From: Pratap Kunwar <pkunwar@GMAIL.COM>
   • DSD and the ending missing values (26 lines)
     From: bbser2009 <bbser2009@GMAIL.COM>

10. Directly reference dataset created view lost the reference?
    • Re: Directly reference dataset created view lost the reference? (178 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Directly reference dataset created view lost the reference? (143 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Directly reference dataset created view lost the reference? (115 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Directly reference dataset created view lost the reference? (74 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

11. FW: Internet2 Connection Established
    • FW: Internet2 Connection Established (18 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

12. Framington Score
    • Re: Framington Score (241 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>

13. Fwd: Much Faster Bootstraps Using SAS? -- Yes, the fastest to date...
    • Re: Fwd: Much Faster Bootstraps Using SAS? -- Yes, the fastest to date... (1521 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Fwd: Much Faster Bootstraps Using SAS? -- Yes, the fastest to date... (1031 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Fwd: Much Faster Bootstraps Using SAS? -- Yes, the fastest to date... (834 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

14. Fwd: Resolving macro variable in macroname
    • Fwd: Resolving macro variable in macroname (132 lines)
      From: Mehul Shah <mehul.sas@GMAIL.COM>

15. Fwd: proc sql
    • Fwd: proc sql (131 lines)
      From: Mehul Shah <mehul.sas@GMAIL.COM>

16. Hash vs OBS= (How to make a tie, not a winner)
    • Re: Hash vs OBS= (How to make a tie, not a winner) (91 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>
    • Re: Hash vs OBS= (How to make a tie, not a winner) (112 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Hash vs OBS= (How to make a tie, not a winner) (86 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Hash vs OBS= (How to make a tie, not a winner) (68 lines)
      From: Andy Arnold <awasas@COX.NET>

17. How to read this instream/raw data
    • Re: How to read this instream/raw data (35 lines)
      From: =?UTF-8?B?6aG+6aOe?= <gufei1984@GMAIL.COM>
    • How to read this instream/raw data (29 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

18. I got it RE: identify starting and ending column numbers
    • I got it RE: identify starting and ending column numbers (42 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

19. ICD9 CM Removing large blocks text
    • Re: ICD9 CM Removing large blocks text (133 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: ICD9 CM Removing large blocks text (13 lines)
      From: Kim Brown <kibrown@LADHS.ORG>
    • ICD9 CM Removing large blocks text (77 lines)
      From: Kim Brown <kibrown@LADHS.ORG>

20. Importing .xlsx files with worksheet names >29 characters
    • Re: Importing .xlsx files with worksheet names >29 characters (29 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Importing .xlsx files with worksheet names >29 characters (28 lines)
      From: Ravi Shanbhag <ravi.m.shanbhag@GMAIL.COM>

21. Incorporating a Baseline Hazard for a Binomial Logit
    • Incorporating a Baseline Hazard for a Binomial Logit (25 lines)
      From: Tanmoy Mukherjee <tkmcornell@YAHOO.COM>

22. Input reading beyond specified length.
    • Re: Input reading beyond specified length. (147 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Input reading beyond specified length. (125 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Input reading beyond specified length. (118 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Input reading beyond specified length. (100 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Input reading beyond specified length. (74 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Input reading beyond specified length. (89 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Input reading beyond specified length. (65 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>

23. Job opening (NYC)
    • Job opening (NYC) (29 lines)
      From: Scott Bucher <sbucher@SCHOOLS.NYC.GOV>

24. NLMIXED Output combinations
    • Re: NLMIXED Output combinations (148 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • NLMIXED Output combinations (62 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>

25. NLMIXED and GLIMMIX -Beta distribution
    • NLMIXED and GLIMMIX -Beta distribution (22 lines)
      From: Pam Shin <pg2003sf@YAHOO.COM>

26. New Computer
    • Re: New Computer (35 lines)
      From: John Birken <zbq5@CDC.GOV>

27. Nonlinear optimization
    • Nonlinear optimization (73 lines)
      From: Amal Muneer <helu.amal@GMAIL.COM>

28. OT: Thursday Theory
    • Re: OT: Thursday Theory (24 lines)
      From: r.hockey@SPH.UQ.EDU.AU
    • OT: Thursday Theory (20 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

29. PRINT fileref in the FILE statement?
    • Re: PRINT fileref in the FILE statement? (88 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: PRINT fileref in the FILE statement? (72 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: PRINT fileref in the FILE statement? (40 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: PRINT fileref in the FILE statement? (37 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • PRINT fileref in the FILE statement? (20 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

30. Parsing regular table
    • Re: Parsing regular table (79 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Parsing regular table (64 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Parsing regular table (45 lines)
      From: Marc Mooney UMN <moon0078@UMN.EDU>

31. Proc Freq Horiz and Verticle lines
    • Proc Freq Horiz and Verticle lines (31 lines)
      From: John Birken <zbq5@CDC.GOV>

32. Proc SQL left join speed being affected significantly by option (rename=)?
    • Re: Proc SQL left join speed being affected significantly by option (rename=)? (64 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Proc SQL left join speed being affected significantly by option (rename=)? (143 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Proc SQL left join speed being affected significantly by option (rename=)? (62 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Proc SQL left join speed being affected significantly by option (rename=)? (70 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Proc SQL left join speed being affected significantly by option (rename=)? (49 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

33. Q: new computer
    • Re: Q: new computer (18 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Q: new computer (23 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

34. RES: understanding spatial autocorrelation
    • RES: understanding spatial autocorrelation (54 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>

35. Resolving macro variable in macroname
    • Re: Resolving macro variable in macroname (152 lines)
      From: Mehul Shah <mehul.sas@GMAIL.COM>
    • Re: Resolving macro variable in macroname (145 lines)
      From: Ian Whitlock <iw1sas@GMAIL.COM>
    • Re: Resolving macro variable in macroname (173 lines)
      From: Mehul Shah <mehul.sas@GMAIL.COM>
    • Re: Resolving macro variable in macroname (159 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Resolving macro variable in macroname (103 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Resolving macro variable in macroname (95 lines)
      From: Mehul Shah <mehul.sas@GMAIL.COM>
    • Re: Resolving macro variable in macroname (53 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Resolving macro variable in macroname (20 lines)
      From: Mehul Shah <mehul.sas@GMAIL.COM>

36. SAS code for calculating Framingham Risk Score
    • Re: SAS code for calculating Framingham Risk Score (28 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • SAS code for calculating Framingham Risk Score (17 lines)
      From: Simcha Pollack <simcha.pollack@CHSLI.ORG>

37. SAS time
    • Re: SAS time (177 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: SAS time (160 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: SAS time (144 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: SAS time (114 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: SAS time (53 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • SAS time (40 lines)
      From: HanJoe Kim <hanjoekim82@GMAIL.COM>

38. Test for measuring trend
    • Re: Test for measuring trend (7 lines)
      From: Eva Pradhan <ep828322@ALBANY.EDU>
    • Re: Test for measuring trend (88 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Test for measuring trend (36 lines)
      From: Eva Pradhan <ep828322@ALBANY.EDU>

39. Use symput to make a macro var
    • Re: Use symput to make a macro var (139 lines)
      From: Xu Libin <Libin.Xu@IRS.GOV>
    • Re: Use symput to make a macro var (107 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Use symput to make a macro var (82 lines)
      From: Xu Libin <Libin.Xu@IRS.GOV>
    • Re: Use symput to make a macro var (68 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Use symput to make a macro var (76 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Use symput to make a macro var (66 lines)
      From: Xu Libin <Libin.Xu@IRS.GOV>

40. Using value of a macro variable into another macro?
    • Re: Using value of a macro variable into another macro? (141 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Using value of a macro variable into another macro? (108 lines)
      From: Xu Libin <Libin.Xu@IRS.GOV>
    • Re: Using value of a macro variable into another macro? (108 lines)
      From: Xu Libin <Libin.Xu@IRS.GOV>
    • Re: Using value of a macro variable into another macro? (79 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Using value of a macro variable into another macro? (95 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Using value of a macro variable into another macro? (70 lines)
      From: Xu Libin <Libin.Xu@IRS.GOV>

41. X and Y in ODS REGION statement (PDF destination)
    • X and Y in ODS REGION statement (PDF destination) (89 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>

42. [Poll] Your analytic career: how do you see yourself at 55?
    • Re: [Poll] Your analytic career: how do you see yourself at 55? (42 lines)
      From: John Burton <jrburtonsaspro@GMAIL.COM>
    • Re: [Poll] Your analytic career: how do you see yourself at 55? (49 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: [Poll] Your analytic career: how do you see yourself at 55? (30 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>
    • [Poll] Your analytic career: how do you see yourself at 55? (14 lines)
      From: Vincent Granville <vincentg@DATASHAPING.COM>

43. appropriate regression model for 12 level categorical response variable?
    • Re: appropriate regression model for 12 level categorical response variable? (21 lines)
      From: Robert Feyerharm <robertf@HEALTH.OK.GOV>

44. change macro variable name dymacro?
    • Re: change macro variable name dymacro? (41 lines)
      From: Jeff <zhujp98@GMAIL.COM>
    • Re: change macro variable name dymacro? (39 lines)
      From: Jeff <zhujp98@GMAIL.COM>
    • Re: change macro variable name dymacro? (33 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: change macro variable name dymacro? (34 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • change macro variable name dymacro? (25 lines)
      From: Jeff <zhujp98@GMAIL.COM>

45. class statement in Proc PRINT
    • Re: class statement in Proc PRINT (77 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: class statement in Proc PRINT (89 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: class statement in Proc PRINT (73 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: class statement in Proc PRINT (74 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • class statement in Proc PRINT (52 lines)
      From: Pratap Kunwar <pkunwar@GMAIL.COM>

46. coefficients for random effects
    • Re: coefficients for random effects (34 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • coefficients for random effects (27 lines)
      From: Thevenet-Morrison, Kelly <Kelly_Thevenet-morrison@URMC.ROCHESTER.EDU>

47. data merging question
    • Re: data merging question (156 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: data merging question (114 lines)
      From: Ian Whitlock <iw1sas@GMAIL.COM>
    • Re: data merging question (71 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: data merging question (59 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: data merging question (61 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: data merging question (67 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • data merging question (42 lines)
      From: Keith Larson <keith.larson@ZOOEKOL.LU.SE>

48. dollar9. and comma9.
    • Re: dollar9. and comma9. (29 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: dollar9. and comma9. (19 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • dollar9. and comma9. (10 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

49. duplicates emails from SAS-L
    • Re: duplicates emails from SAS-L (67 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: duplicates emails from SAS-L (45 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: duplicates emails from SAS-L (46 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: duplicates emails from SAS-L (51 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: duplicates emails from SAS-L (38 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: duplicates emails from SAS-L (29 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: duplicates emails from SAS-L (35 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: duplicates emails from SAS-L (31 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: duplicates emails from SAS-L (30 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • duplicates emails from SAS-L (19 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

50. equivalent of an offset in proc mixed
    • Re: equivalent of an offset in proc mixed (168 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: equivalent of an offset in proc mixed (148 lines)
      From: Keith Larson <keith.larson@ZOOEKOL.LU.SE>
    • Re: equivalent of an offset in proc mixed (8 lines)
      From: SUBSCRIBE SAS-L JingJu11 S <jingju11@HOTMAIL.COM>
    • Re: equivalent of an offset in proc mixed (88 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • equivalent of an offset in proc mixed (33 lines)
      From: Keith Larson <keith.larson@ZOOEKOL.LU.SE>

51. file shortcuts question remade
    • Re: file shortcuts question remade (61 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • file shortcuts question remade (43 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

52. formatted input vs column input
    • formatted input vs column input (16 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

53. funny code, formatted input or list input or neither
    • Re: funny code, formatted input or list input or neither (78 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • funny code, formatted input or list input or neither (50 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

54. how to convert one variable into multiple columns according its value?
    • Re: how to convert one variable into multiple columns according its value? (33 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • how to convert one variable into multiple columns according its value? (15 lines)
      From: Zibiao Zhang <zzhang@HSPH.HARVARD.EDU>

55. how to get macro variable length
    • Re: how to get macro variable length (39 lines)
      From: Ian Whitlock <iw1sas@GMAIL.COM>
    • Re: how to get macro variable length (35 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: how to get macro variable length (31 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • how to get macro variable length (16 lines)
      From: Jeff <zhujp98@GMAIL.COM>

56. identify starting and ending column numbers
    • Re: identify starting and ending column numbers (76 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: identify starting and ending column numbers (81 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: identify starting and ending column numbers (56 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: identify starting and ending column numbers (90 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: identify starting and ending column numbers (76 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: identify starting and ending column numbers (66 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: identify starting and ending column numbers (49 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: identify starting and ending column numbers (56 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: identify starting and ending column numbers (30 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: identify starting and ending column numbers (55 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • identify starting and ending column numbers (21 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

57. input statement vs. put statement
    • Re: input statement vs. put statement (64 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • input statement vs. put statement (23 lines)
      From: Kyungtae Kim <joey.kyung.kim@GMAIL.COM>

58. length of numeric variables
    • Re: length of numeric variables (243 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: length of numeric variables (216 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: length of numeric variables (20 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: length of numeric variables (200 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>
    • Re: length of numeric variables (186 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: length of numeric variables (255 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: length of numeric variables (195 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: length of numeric variables (159 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: length of numeric variables (177 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: length of numeric variables (242 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: length of numeric variables (185 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: length of numeric variables (98 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

59. new computer
    • Re: new computer (31 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: new computer (65 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: new computer (37 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>

60. output, loop, PDV
    • Re: output, loop, PDV (132 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: output, loop, PDV (79 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • output, loop, PDV (61 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

61. proc report
    • Re: proc report (66 lines)
      From: Masoud Pajoh <mpajoh@ODOT.ORG>
    • Re: proc report (46 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • proc report (27 lines)
      From: Masoud Pajoh <mpajoh@ODOT.ORG>

62. proc sql
    • Re: proc sql (151 lines)
      From: Fatos US <fatosus@GMAIL.COM>
    • Re: proc sql (51 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: proc sql (119 lines)
      From: Mehul Shah <mehul.sas@GMAIL.COM>
    • Re: proc sql (51 lines)
      From: Mehul Shah <mehul.sas@GMAIL.COM>
    • Re: proc sql (51 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • proc sql (35 lines)
      From: Fatos US <fatosus@GMAIL.COM>

63. random functions
    • Re: random functions (56 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: random functions (23 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • random functions (9 lines)
      From: Youngdeok Kim <yk2k@MTMAIL.MTSU.EDU>

64. reminder: EG v4.1 dies on Dec 1, 2010
    • reminder: EG v4.1 dies on Dec 1, 2010 (33 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

65. the d value of an informat, as in w.d or comma9.d
    • Re: the d value of an informat, as in w.d or comma9.d (81 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>
    • Re: the d value of an informat, as in w.d or comma9.d (42 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: the d value of an informat, as in w.d or comma9.d (49 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • the d value of an informat, as in w.d or comma9.d (22 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

66. variable-length records
    • Re: variable-length records (76 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: variable-length records (38 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • variable-length records (18 lines)
      From: bbser2009 <bbser2009@GMAIL.COM>

67. versions of SAS 9.2
    • Re: versions of SAS 9.2 (18 lines)
      From: r.hockey@SPH.UQ.EDU.AU
    • Re: versions of SAS 9.2 (34 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: versions of SAS 9.2 (19 lines)
      From: Josh Di Gennaro <digennjp@GMAIL.COM>
    • versions of SAS 9.2 (12 lines)
      From: Joe Kelley <jkelley@UGA.EDU>