Table of contents:

• =?utf-8?B?UmU6IFVzaW5nIHRoZSAic2V0IiBmdW5jdGlvbiBpbiBhIE1hY3Jv?=
• Automatic reply: SAS INFILEing a perl program using a PIPE
• Automatic reply: SAS-L Digest - 1 Aug 2010 to 2 Aug 2010 (#2010-881)
• Automatic reply: SAS-L Digest - 4 Aug 2010 to 5 Aug 2010 (#2010-889)
• Chance to Make SAS-L History: Did You Know That...
• Clinical/Pharma SAS Programmers required Europe
• Connect Script File: Defaulting the user ID
• Data steps arrays & REG (3 messages)
• Datasteps arrays & Proc reg (3 messages)
• Difference between VAR,ID,BY,CLASS
• Displaying all textual data in a table (7 messages)
• End of file (4 messages)
• Excel frontend with SAS engine (3 messages)
• FTP an Excel file (8 messages)
• GENMOD SAS code
• IE8 and SAS 9.13
• Is 9.2 THAT much faster than 9.1.3 (12 messages)
• M2010 Data Mining Conference, Oct. 25-26 Caesars Palace, Las Vegas: www.sas.com/m2010.
• Mixed model - random terms
• More on list vs private responses (4 messages)
• Multiple Imputation: Scoring new data
• Non Significant Overall Anova versus Significant Type IV
• Optimizing SAS to run faster (9 messages)
• Overall Anova or Type IV
• PASSTHRU SQL Question (11 messages)
• PROC FREQ - how do you limit the number of levels in the output? (3 messages)
• Passing paramters to SAS under z/OS batch (4 messages)
• PhUSE - SDE Boston - FDA Statistical Reviewer Viewpoint on Standards
• Problem counting by case (4 messages)
• Problem counting cases etc.
• Proc SUMMARY output dataset (12 messages)
• Proc reg (6 messages)
• Random Effects question (10 messages)
• Resized Command Bar
• SAS INFILEing a perl program using a PIPE (8 messages)
• SAS Statistics
• SAS datasets into multiple excel sheets, with labels (3 messages)
• SAS position, salary up to 90K
• Sample Size Determination. Online Course Starts Friday
• Sample Weighting in NLMIXED - Possible?
• Significant vs Non-Significant Effects (2 messages)
• Simple Graph Question
• Spanish Speaking SAS Programmer Wanted Toronto
• TABULATE: col % at the sub-total level (2 messages)
• Transposing data (14 messages)
• Using the "set" function in a Macro (5 messages)
• Validation KS Statistics (3 messages)
• WUSS 2010 Conference Registration - NOW OPEN!
• Western Users of SAS Software
• What do we have to do to SAVE SAS-L (48 messages)
• Why you should always use a RUN statement (A SAS Gotcha)
• convert a charater variable int SAS date (3 messages)
• fwd: R on reddit
• how solve this this senario? (2 messages)
• how to reslove date conflicts when some date ranges are overlaped
• how to stack 2 different folders.
• how to turn multiple rows into one row in group? (6 messages)
• large changes in coefficients (3 messages)
• question on first events: pasted data layout and code (2 messages)

1. =?utf-8?B?UmU6IFVzaW5nIHRoZSAic2V0IiBmdW5jdGlvbiBpbiBhIE1hY3Jv?=
   • =?utf-8?B?UmU6IFVzaW5nIHRoZSAic2V0IiBmdW5jdGlvbiBpbiBhIE1hY3Jv?= (56 lines)
     From: =?utf-8?B?dG9ieWR1bm5AaG90bWFpbC5jb20=?= <tobydunn@HOTMAIL.COM>

2. Automatic reply: SAS INFILEing a perl program using a PIPE
   • Automatic reply: SAS INFILEing a perl program using a PIPE (12 lines)
     From: Remillard, Nancybelle <nremilla@INDIANA.EDU>

3. Automatic reply: SAS-L Digest - 1 Aug 2010 to 2 Aug 2010 (#2010-881)
   • Automatic reply: SAS-L Digest - 1 Aug 2010 to 2 Aug 2010 (#2010-881) (13 lines)
     From: Jones, Kendra Elizabeth <joneskee@IUPUI.EDU>

4. Automatic reply: SAS-L Digest - 4 Aug 2010 to 5 Aug 2010 (#2010-889)
   • Automatic reply: SAS-L Digest - 4 Aug 2010 to 5 Aug 2010 (#2010-889) (22 lines)
     From: Peel,Jennifer <Jennifer.Peel@COLOSTATE.EDU>

5. Chance to Make SAS-L History: Did You Know That...
   • Re: Chance to Make SAS-L History: Did You Know That... (90 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>

6. Clinical/Pharma SAS Programmers required Europe
   • Clinical/Pharma SAS Programmers required Europe (28 lines)
     From: Mark James <mark.james@VETICA-RESOURCE.CO.UK>

7. Connect Script File: Defaulting the user ID
   • Re: Connect Script File: Defaulting the user ID (120 lines)
     From: Graham Murray <graham.murray@WEBMINER.CO.UK>

8. Data steps arrays & REG
   • Data steps arrays & REG (59 lines)
     From: Jake Adamson <Jake.Adamson@SQA.ORG.UK>
   • Re: Data steps arrays & REG (87 lines)
     From: Arthur Tabachneck <art297@NETSCAPE.NET>
   • Re: Data steps arrays & REG (188 lines)
     From: Arthur Tabachneck <art297@NETSCAPE.NET>

9. Datasteps arrays & Proc reg
   • Datasteps arrays & Proc reg (114 lines)
     From: Jake Adamson <Jake.Adamson@SQA.ORG.UK>
   • Re: Datasteps arrays & Proc reg (222 lines)
     From: Jake Adamson <Jake.Adamson@SQA.ORG.UK>
   • Re: Datasteps arrays & Proc reg (286 lines)
     From: Arthur Tabachneck <art297@NETSCAPE.NET>

10. Difference between VAR,ID,BY,CLASS
    • Re: Difference between VAR,ID,BY,CLASS (76 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>

11. Displaying all textual data in a table
    • Displaying all textual data in a table (56 lines)
      From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>
    • Re: Displaying all textual data in a table (98 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
    • Re: Displaying all textual data in a table (70 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Displaying all textual data in a table (74 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Displaying all textual data in a table (116 lines)
      From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>
    • Re: Displaying all textual data in a table (88 lines)
      From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>
    • Re: Displaying all textual data in a table (134 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>

12. End of file
    • End of file (67 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: End of file (81 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: End of file (87 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: End of file (96 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>

13. Excel frontend with SAS engine
    • Re: Excel frontend with SAS engine (53 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: Excel frontend with SAS engine (94 lines)
      From: Alan Churchill <alan.churchill@SAVIAN.NET>
    • Re: Excel frontend with SAS engine (154 lines)
      From: ajay ohri <ajayohri@YAHOO.COM>

14. FTP an Excel file
    • FTP an Excel file (32 lines)
      From: Louis Rheault <Louis-Rene.Rheault@REG.ULAVAL.CA>
    • Re: FTP an Excel file (68 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: FTP an Excel file (110 lines)
      From: Louis-Ren� Rheault <Louis-Rene.Rheault@REG.ULAVAL.CA>
    • Re: FTP an Excel file (73 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: FTP an Excel file (44 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: FTP an Excel file (112 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
    • Re: FTP an Excel file (120 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: FTP an Excel file (144 lines)
      From: Louis Rheault <Louis-rene.Rheault@REG.ULAVAL.CA>

15. GENMOD SAS code
    • GENMOD SAS code (27 lines)
      From: Srikanth <sgoli.sas@GMAIL.COM>

16. IE8 and SAS 9.13
    • IE8 and SAS 9.13 (9 lines)
      From: Jenine Milum <jenine.milum@WACHOVIA.COM>

17. Is 9.2 THAT much faster than 9.1.3
    • Is 9.2 THAT much faster than 9.1.3 (28 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: Is 9.2 THAT much faster than 9.1.3 (52 lines)
      From: Gregg Snell <sas@DATASAVANTCONSULTING.COM>
    • Re: Is 9.2 THAT much faster than 9.1.3 (64 lines)
      From: Ken Barz <zrab123@COMCAST.NET>
    • Re: Is 9.2 THAT much faster than 9.1.3 (52 lines)
      From: Daniel Nordlund <djnordlund@VERIZON.NET>
    • Re: Is 9.2 THAT much faster than 9.1.3 (79 lines)
      From: Andre Wielki <wielki@INED.FR>
    • Re: Is 9.2 THAT much faster than 9.1.3 (22 lines)
      From: George Joseph <gjman@HOTMAIL.COM>
    • Re: Is 9.2 THAT much faster than 9.1.3 (54 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Is 9.2 THAT much faster than 9.1.3 (73 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Is 9.2 THAT much faster than 9.1.3 (68 lines)
      From: Philip Rack <PhilRack@MINEQUEST.COM>
    • Re: Is 9.2 THAT much faster than 9.1.3 (41 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: Is 9.2 THAT much faster than 9.1.3 (71 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: Is 9.2 THAT much faster than 9.1.3 (58 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

18. M2010 Data Mining Conference, Oct. 25-26 Caesars Palace, Las Vegas: www.sas.com/m2010.
    • M2010 Data Mining Conference, Oct. 25-26 Caesars Palace, Las Vegas: www.sas.com/m2010. (25 lines)
      From: Vincent Granville <vincentg@DATASHAPING.COM>

19. Mixed model - random terms
    • Mixed model - random terms (63 lines)
      From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>

20. More on list vs private responses
    • More on list vs private responses (27 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: More on list vs private responses (48 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: More on list vs private responses (91 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: More on list vs private responses (24 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

21. Multiple Imputation: Scoring new data
    • Re: Multiple Imputation: Scoring new data (40 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

22. Non Significant Overall Anova versus Significant Type IV
    • Non Significant Overall Anova versus Significant Type IV (18 lines)
      From: Billy Thompson <bill.thompson@BROOKS.AF.MIL>

23. Optimizing SAS to run faster
    • Optimizing SAS to run faster (21 lines)
      From: P. Cristian Gugiu <crisgugiu@YAHOO.COM>
    • Re: Optimizing SAS to run faster (44 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: Optimizing SAS to run faster (40 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: Optimizing SAS to run faster (30 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: Optimizing SAS to run faster (8 lines)
      From: P. Cristian Gugiu <crisgugiu@YAHOO.COM>
    • Re: Optimizing SAS to run faster (26 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: Optimizing SAS to run faster (18 lines)
      From: P. Cristian Gugiu <crisgugiu@YAHOO.COM>
    • Re: Optimizing SAS to run faster (37 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Optimizing SAS to run faster (28 lines)
      From: P. Cristian Gugiu <crisgugiu@YAHOO.COM>

24. Overall Anova or Type IV
    • Overall Anova or Type IV (10 lines)
      From: Billy Thompson <bill.thompson@BROOKS.AF.MIL>

25. PASSTHRU SQL Question
    • PASSTHRU SQL Question (40 lines)
      From: Dave Brewer <david.brewer@UC.EDU>
    • Re: PASSTHRU SQL Question (63 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: PASSTHRU SQL Question (17 lines)
      From: Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM>
    • Re: PASSTHRU SQL Question (128 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: PASSTHRU SQL Question (161 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: PASSTHRU SQL Question (101 lines)
      From: Dave Brewer <david.brewer@UC.EDU>
    • Re: PASSTHRU SQL Question (26 lines)
      From: Dave Brewer <david.brewer@UC.EDU>
    • Re: PASSTHRU SQL Question (214 lines)
      From: Dave Brewer <david.brewer@UC.EDU>
    • Re: PASSTHRU SQL Question (39 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: PASSTHRU SQL Question (44 lines)
      From: Dave Brewer <david.brewer@UC.EDU>
    • Re: PASSTHRU SQL Question (96 lines)
      From: Paul Dorfman <sashole@BELLSOUTH.NET>

26. PROC FREQ - how do you limit the number of levels in the output?
    • PROC FREQ - how do you limit the number of levels in the output? (20 lines)
      From: Jeff Carpenter <wess.carpenter@GMAIL.COM>
    • Re: PROC FREQ - how do you limit the number of levels in the output? (67 lines)
      From: Jack Clark <jclark@HILLTOP.UMBC.EDU>
    • Re: PROC FREQ - how do you limit the number of levels in the output? (51 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

27. Passing paramters to SAS under z/OS batch
    • Passing paramters to SAS under z/OS batch (37 lines)
      From: =?windows-1255?Q?=E2=E3=E9_=E1=EF_=E0=E1=E9?= <GADI_B@MALAM.COM>
    • Re: Passing paramters to SAS under z/OS batch (47 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Passing paramters to SAS under z/OS batch (60 lines)
      From: =?windows-1255?Q?=E2=E3=E9_=E1=EF_=E0=E1=E9?= <GADI_B@MALAM.COM>
    • Re: Passing paramters to SAS under z/OS batch (47 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

28. PhUSE - SDE Boston - FDA Statistical Reviewer Viewpoint on Standards
    • PhUSE - SDE Boston - FDA Statistical Reviewer Viewpoint on Standards (66 lines)
      From: Dan <djboisvert@HOTMAIL.COM>

29. Problem counting by case
    • Problem counting by case (38 lines)
      From: dave crimkey <d_crimkey@YAHOO.COM>
    • Re: Problem counting by case (60 lines)
      From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM>
    • Re: Problem counting by case (108 lines)
      From: shyamprasad samisetti <shyam.cbz@GMAIL.COM>
    • Re: Problem counting by case (48 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>

30. Problem counting cases etc.
    • Problem counting cases etc. (14 lines)
      From: dave crimkey <d_crimkey@YAHOO.COM>

31. Proc SUMMARY output dataset
    • Proc SUMMARY output dataset (21 lines)
      From: Richard DeVenezia <rdevenezia@GMAIL.COM>
    • Re: Proc SUMMARY output dataset (122 lines)
      From: Jack Clark <jclark@HILLTOP.UMBC.EDU>
    • Re: Proc SUMMARY output dataset (92 lines)
      From: Jack Clark <jclark@HILLTOP.UMBC.EDU>
    • Re: Proc SUMMARY output dataset (52 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Proc SUMMARY output dataset (90 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: Proc SUMMARY output dataset (97 lines)
      From: Jack Clark <jclark@HILLTOP.UMBC.EDU>
    • Re: Proc SUMMARY output dataset (74 lines)
      From: Richard DeVenezia <rdevenezia@GMAIL.COM>
    • Re: Proc SUMMARY output dataset (130 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Proc SUMMARY output dataset (114 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Proc SUMMARY output dataset (88 lines)
      From: Mike Zdeb <msz03@ALBANY.EDU>
    • Re: Proc SUMMARY output dataset (90 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Proc SUMMARY output dataset (103 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>

32. Proc reg
    • Proc reg (58 lines)
      From: Jake Adamson <Jake.Adamson@SQA.ORG.UK>
    • Re: Proc reg (93 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Proc reg (118 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: Proc reg (160 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Proc reg (182 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Proc reg (110 lines)
      From: Jake Adamson <Jake.Adamson@SQA.ORG.UK>

33. Random Effects question
    • Random Effects question (30 lines)
      From: Andrew Agrimson <jagrimsasl@GMAIL.COM>
    • Re: Random Effects question (50 lines)
      From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>
    • Re: Random Effects question (73 lines)
      From: Andrew Agrimson <jagrimsasl@GMAIL.COM>
    • Re: Random Effects question (96 lines)
      From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>
    • Re: Random Effects question (85 lines)
      From: Ryan Black <ryan.andrew.black@GMAIL.COM>
    • Re: Random Effects question (111 lines)
      From: Andrew Agrimson <jagrimsasl@GMAIL.COM>
    • Re: Random Effects question (138 lines)
      From: Ryan Black <ryan.andrew.black@GMAIL.COM>
    • Re: Random Effects question (162 lines)
      From: Andrew Agrimson <jagrimsasl@GMAIL.COM>
    • Re: Random Effects question (203 lines)
      From: Ryan Black <ryan.andrew.black@GMAIL.COM>
    • Re: Random Effects question (236 lines)
      From: Andrew Agrimson <jagrimsasl@GMAIL.COM>

34. Resized Command Bar
    • Re: Resized Command Bar (27 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>

35. SAS INFILEing a perl program using a PIPE
    • SAS INFILEing a perl program using a PIPE (125 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: SAS INFILEing a perl program using a PIPE (24 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: SAS INFILEing a perl program using a PIPE (83 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: SAS INFILEing a perl program using a PIPE (109 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: SAS INFILEing a perl program using a PIPE (60 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: SAS INFILEing a perl program using a PIPE (231 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: SAS INFILEing a perl program using a PIPE (77 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: SAS INFILEing a perl program using a PIPE (259 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>

36. SAS Statistics
    • Re: SAS Statistics (69 lines)
      From: saslearn chicago <sasswamy@GMAIL.COM>

37. SAS datasets into multiple excel sheets, with labels
    • SAS datasets into multiple excel sheets, with labels (18 lines)
      From: Shukla Kshirsagar <shuklak@HOTMAIL.COM>
    • Re: SAS datasets into multiple excel sheets, with labels (58 lines)
      From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM>
    • Re: SAS datasets into multiple excel sheets, with labels (41 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

38. SAS position, salary up to 90K
    • SAS position, salary up to 90K (85 lines)
      From: Vincent Granville <vincentg@DATASHAPING.COM>

39. Sample Size Determination. Online Course Starts Friday
    • Sample Size Determination. Online Course Starts Friday (21 lines)
      From: Dorothy Middleton <courses@STATCOURSE.COM>

40. Sample Weighting in NLMIXED - Possible?
    • Sample Weighting in NLMIXED - Possible? (35 lines)
      From: Ryan Black <ryan.andrew.black@GMAIL.COM>

41. Significant vs Non-Significant Effects
    • Significant vs Non-Significant Effects (12 lines)
      From: Billy Thompson <bill.thompson@BROOKS.AF.MIL>
    • Re: Significant vs Non-Significant Effects (76 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>

42. Simple Graph Question
    • Simple Graph Question (51 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>

43. Spanish Speaking SAS Programmer Wanted Toronto
    • Re: Spanish Speaking SAS Programmer Wanted Toronto (30 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>

44. TABULATE: col % at the sub-total level
    • TABULATE: col % at the sub-total level (53 lines)
      From: Miller, Jeremy T. (CDC/OID/NCPDCID) <zyp9@CDC.GOV>
    • Re: TABULATE: col % at the sub-total level (113 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>

45. Transposing data
    • Transposing data (21 lines)
      From: Billy Thompson <bill.thompson@BROOKS.AF.MIL>
    • Re: Transposing data (34 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • Re: Transposing data (83 lines)
      From: Billy Thompson <bill.thompson@BROOKS.AF.MIL>
    • Re: Transposing data (126 lines)
      From: KRISHNAMURTHY, SUBASH [AG/1000] <subash.krishnamurthy@MONSANTO.COM>
    • Re: Transposing data (157 lines)
      From: Billy Thompson <bill.thompson@BROOKS.AF.MIL>
    • Re: Transposing data (162 lines)
      From: Jewell, Adria <ajewell@RAND.ORG>
    • Re: Transposing data (12 lines)
      From: Billy Thompson <bill.thompson@BROOKS.AF.MIL>
    • Re: Transposing data (167 lines)
      From: Adria Jewell <ajewell@RAND.ORG>
    • Re: Transposing data (35 lines)
      From: Jewell, Adria <ajewell@RAND.ORG>
    • Re: Transposing data (9 lines)
      From: Billy Thompson <bill.thompson@BROOKS.AF.MIL>
    • Re: Transposing data (49 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: Transposing data (289 lines)
      From: Ian Whitlock <iw1sas@GMAIL.COM>
    • Re: Transposing data (294 lines)
      From: Ian Whitlock <iw1sas@GMAIL.COM>
    • Re: Transposing data (12 lines)
      From: Ian Whitlock <iw1sas@GMAIL.COM>

46. Using the "set" function in a Macro
    • Using the "set" function in a Macro (57 lines)
      From: Deb <detemkin@GMAIL.COM>
    • Re: Using the "set" function in a Macro (74 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: Using the "set" function in a Macro (110 lines)
      From: Deborah Temkin <dzt102@PSU.EDU>
    • Re: Using the "set" function in a Macro (122 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Using the "set" function in a Macro (40 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>

47. Validation KS Statistics
    • Validation KS Statistics (12 lines)
      From: Samuel Jackson <arlando20002000@YAHOO.COM>
    • Re: Validation KS Statistics (20 lines)
      From: Jonas Bilenas <jonas.bilenas@CHASE.COM>
    • Re: Validation KS Statistics (11 lines)
      From: Samuel Jackson <arlando20002000@YAHOO.COM>

48. WUSS 2010 Conference Registration - NOW OPEN!
    • WUSS 2010 Conference Registration - NOW OPEN! (67 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

49. Western Users of SAS Software
    • Western Users of SAS Software (10 lines)
      From: Vincent Granville <vincentg@DATASHAPING.COM>

50. What do we have to do to SAVE SAS-L
    • What do we have to do to SAVE SAS-L (18 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: What do we have to do to SAVE SAS-L (38 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: What do we have to do to SAVE SAS-L (70 lines)
      From: ajay ohri <ajayohri@YAHOO.COM>
    • Re: What do we have to do to SAVE SAS-L (96 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: What do we have to do to SAVE SAS-L (54 lines)
      From: Annamaria Rousey <ademars@USC.EDU>
    • Re: What do we have to do to SAVE SAS-L (53 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: What do we have to do to SAVE SAS-L (48 lines)
      From: Alan Churchill <alan.churchill@SAVIAN.NET>
    • Re: What do we have to do to SAVE SAS-L (35 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: What do we have to do to SAVE SAS-L (52 lines)
      From: Alan Churchill <alan.churchill@SAVIAN.NET>
    • Re: What do we have to do to SAVE SAS-L (82 lines)
      From: Philip Rack <PhilRack@MINEQUEST.COM>
    • Re: What do we have to do to SAVE SAS-L (133 lines)
      From: Jake Adamson <Jake.Adamson@SQA.ORG.UK>
    • Re: What do we have to do to SAVE SAS-L (50 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>
    • Re: What do we have to do to SAVE SAS-L (63 lines)
      From: Andre Wielki <wielki@INED.FR>
    • Re: What do we have to do to SAVE SAS-L (71 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: What do we have to do to SAVE SAS-L (20 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: What do we have to do to SAVE SAS-L (21 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: What do we have to do to SAVE SAS-L (37 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: What do we have to do to SAVE SAS-L (28 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: What do we have to do to SAVE SAS-L (52 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: What do we have to do to SAVE SAS-L (47 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: What do we have to do to SAVE SAS-L (126 lines)
      From: Andrew Howell <info@ANJGROUP.NET.AU>
    • Re: What do we have to do to SAVE SAS-L (51 lines)
      From: Teed, Lionel <Lionel.Teed@TD.COM>
    • Re: What do we have to do to SAVE SAS-L (52 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: What do we have to do to SAVE SAS-L (35 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: What do we have to do to SAVE SAS-L (58 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: What do we have to do to SAVE SAS-L (83 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: What do we have to do to SAVE SAS-L (88 lines)
      From: Annmaria Demars <ademars@USC.EDU>
    • Re: What do we have to do to SAVE SAS-L (69 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: What do we have to do to SAVE SAS-L (98 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: What do we have to do to SAVE SAS-L (55 lines)
      From: Ken Barz <zrab123@COMCAST.NET>
    • Re: What do we have to do to SAVE SAS-L (38 lines)
      From: r.hockey@SPH.UQ.EDU.AU
    • Re: What do we have to do to SAVE SAS-L (158 lines)
      From: Teed, Lionel <Lionel.Teed@TD.COM>
    • Re: What do we have to do to SAVE SAS-L (218 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: What do we have to do to SAVE SAS-L (112 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: What do we have to do to SAVE SAS-L (39 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: What do we have to do to SAVE SAS-L (35 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: What do we have to do to SAVE SAS-L (32 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: What do we have to do to SAVE SAS-L (48 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: What do we have to do to SAVE SAS-L (59 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: What do we have to do to SAVE SAS-L (81 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: What do we have to do to SAVE SAS-L (58 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: What do we have to do to SAVE SAS-L (110 lines)
      From: Teed, Lionel <Lionel.Teed@TD.COM>
    • Re: What do we have to do to SAVE SAS-L (109 lines)
      From: Teed, Lionel <Lionel.Teed@TD.COM>
    • Re: What do we have to do to SAVE SAS-L (180 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: What do we have to do to SAVE SAS-L (124 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: What do we have to do to SAVE SAS-L (144 lines)
      From: Lamias, Mark (CDC/OID/OD) (CTR) <bnz6@CDC.GOV>
    • Re: What do we have to do to SAVE SAS-L (186 lines)
      From: Florio Arguillas <foa2@CORNELL.EDU>
    • Re: What do we have to do to SAVE SAS-L (12 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>

51. Why you should always use a RUN statement (A SAS Gotcha)
    • Re: Why you should always use a RUN statement (A SAS Gotcha) (144 lines)
      From: Andre Wielki <wielki@INED.FR>

52. convert a charater variable int SAS date
    • convert a charater variable int SAS date (22 lines)
      From: haiyan chen <haiyan_c@YAHOO.COM>
    • Re: convert a charater variable int SAS date (43 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: convert a charater variable int SAS date (42 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>

53. fwd: R on reddit
    • fwd: R on reddit (16 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

54. how solve this this senario?
    • how solve this this senario? (28 lines)
      From: Nway <hymadsk@GMAIL.COM>
    • Re: how solve this this senario? (88 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>

55. how to reslove date conflicts when some date ranges are overlaped
    • Re: how to reslove date conflicts when some date ranges are overlaped (102 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>

56. how to stack 2 different folders.
    • Re: how to stack 2 different folders. (117 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

57. how to turn multiple rows into one row in group?
    • how to turn multiple rows into one row in group? (47 lines)
      From: Jeff <zhujp98@GMAIL.COM>
    • Re: how to turn multiple rows into one row in group? (90 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: how to turn multiple rows into one row in group? (105 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: how to turn multiple rows into one row in group? (60 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: how to turn multiple rows into one row in group? (118 lines)
      From: Jeff <zhujp98@GMAIL.COM>
    • Re: how to turn multiple rows into one row in group? (71 lines)
      From: Jeff <zhujp98@GMAIL.COM>

58. large changes in coefficients
    • large changes in coefficients (32 lines)
      From: Myung <dopraxis@GMAIL.COM>
    • Re: large changes in coefficients (38 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: large changes in coefficients (57 lines)
      From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU>

59. question on first events: pasted data layout and code
    • Re: question on first events: pasted data layout and code (84 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: question on first events: pasted data layout and code (150 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>