Table of contents:

• '01'x ? (4 messages)
• 95%ci for a single percentage (2 messages)
• Automatic reply: SAS-L Digest - 2 Nov 2011 to 3 Nov 2011 (#2011-963)
• Automatic reply: SAS-L Digest - 4 Nov 2011 - Special issue (#2011-967)
• Cox regression - repeated measures?? (3 messages)
• Data Step: how to throw error on missing dataset in SET? (7 messages)
• Data step question: why different results (4 messages)
• EXCELXP Tagset Question - Telling Excel to Keep a Variable as Text (to preserve leading zeros) (2 messages)
• Equivalent of "top" command in command line for the enhanced editor (3 messages)
• Error trying to establish ODBC connection between SAS and SQL Server
• File Upload Interface on SAS Report Delivery Portal
• Find department with most employees (12 messages)
• Friday humor (on Wed) (statistics) (7 messages)
• Fwd: Question For The Financially Astute
• GLIMMIX - Standardized Residuals (3 messages)
• GML in SAS and R (3 messages)
• Global Assessment of Functioning?
• Help in destringing mult vars then recoding into new indicator vars (2 messages)
• Inserting Values (12 messages)
• Lagging Groups
• Linux rbrowser in multiuser environment
• List of Variables through empty PDV (5 messages)
• Lost Card Question (2 messages)
• Lost Card Question (please see this one) (7 messages)
• ODS HTML "Relative" paths
• ODS HTML tagset: Freeze column and scroll (5 messages)
• OT: Modifying SAS Explorer's view in Excel (3 messages)
• Old data rescue (French CLOTILDE software)
• Passing a variable value as condition into a where clause (10 messages)
• Random Intercept and Slope Models
• Reshape data so that each category becomes a new variable (17 messages)
• SAS Job (10-12 hours with good hourly rate)
• SAS Job (only for 10-12 hours)
• SAS is recognizing dataasets on one computer and not another (6 messages)
• SPDS Table:Locale Error
• Sgdesign (10 messages)
• Special Characters (6 messages)
• Systematic Jittering? (8 messages)
• Trend Analysis in Proportions using NLMIXED (8 messages)
• Trend in Proportions via NLMIXED (A Simulation Experiment) (2 messages)
• WPS (2 messages)
• Wide CI but good power? (4 messages)
• an issue in 9.3 sgplot -loess (2 messages)
• auto-scheduling a program to run (5 messages)
• comparison of proportions (2 messages)
• connecting to SQL Server / connection=shared
• most efficient way to connect to sql server from sas (8 messages)
• need helps for data mamipulation (3 messages)
• ods/pdf anchor, can it be done with BY processing?
• proc report and row color (5 messages)
• question for MIANALYZE
• question for users of R+SAS (7 messages)
• quick ata step (3 messages)
• reading a comma *.csv file, convert it to a flat file, scale from 0-5 to 1-6 and blanks to be spaces. (3 messages)
• something interesting about INFILE and SET statements (3 messages)
• special character
• unsubscribe (2 messages)

1. '01'x ?
   • '01'x ? (15 lines)
     From: bbser 2009 <bbser2009@GMAIL.COM>
   • Re: '01'x ? (20 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: '01'x ? (21 lines)
     From: Mark Miller <mdhmiller@GMAIL.COM>
   • Re: '01'x ? (26 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>

2. 95%ci for a single percentage
   • 95%ci for a single percentage (17 lines)
     From: Christine <christinepeloquin1@GMAIL.COM>
   • Re: 95%ci for a single percentage (53 lines)
     From: Bross, Dean S <dean.bross@VA.GOV>

3. Automatic reply: SAS-L Digest - 2 Nov 2011 to 3 Nov 2011 (#2011-963)
   • Automatic reply: SAS-L Digest - 2 Nov 2011 to 3 Nov 2011 (#2011-963) (16 lines)
     From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU>

4. Automatic reply: SAS-L Digest - 4 Nov 2011 - Special issue (#2011-967)
   • Automatic reply: SAS-L Digest - 4 Nov 2011 - Special issue (#2011-967) (20 lines)
     From: Carol Olson <Carol.Olson@MEREDITH.COM>

5. Cox regression - repeated measures??
   • Cox regression - repeated measures?? (17 lines)
     From: Michelle Secic <consult@SECICSTATS.COM>
   • Re: Cox regression - repeated measures?? (21 lines)
     From: Cornel Lencar <clencar@INTERCHANGE.UBC.CA>
   • Re: Cox regression - repeated measures?? (70 lines)
     From: Viel, Kevin <kviel@SJHA.ORG>

6. Data Step: how to throw error on missing dataset in SET?
   • Data Step: how to throw error on missing dataset in SET? (63 lines)
     From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
   • Re: Data Step: how to throw error on missing dataset in SET? (68 lines)
     From: Tom Abernathy <tom.abernathy@GMAIL.COM>
   • Re: Data Step: how to throw error on missing dataset in SET? (137 lines)
     From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
   • Re: Data Step: how to throw error on missing dataset in SET? (150 lines)
     From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
   • Re: Data Step: how to throw error on missing dataset in SET? (22 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: Data Step: how to throw error on missing dataset in SET? (46 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: Data Step: how to throw error on missing dataset in SET? (46 lines)
     From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

7. Data step question: why different results
   • Data step question: why different results (109 lines)
     From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
   • Re: Data step question: why different results (137 lines)
     From: Yu Zhang <zhangyu05@GMAIL.COM>
   • Re: Data step question: why different results (152 lines)
     From: Mike Rhoads <RHOADSM1@WESTAT.COM>
   • Re: Data step question: why different results (143 lines)
     From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>

8. EXCELXP Tagset Question - Telling Excel to Keep a Variable as Text (to preserve leading zeros)
   • Re: EXCELXP Tagset Question - Telling Excel to Keep a Variable as Text (to preserve leading zeros) (12 lines)
     From: Paul St Louis <paul.stlouis@TXDOT.GOV>
   • Re: EXCELXP Tagset Question - Telling Excel to Keep a Variable as Text (to preserve leading zeros) (17 lines)
     From: Tom Abernathy <tom.abernathy@GMAIL.COM>

9. Equivalent of "top" command in command line for the enhanced editor
   • Equivalent of "top" command in command line for the enhanced editor (22 lines)
     From: Francis Dwyer <franwdwyer@GOOGLEMAIL.COM>
   • Re: Equivalent of "top" command in command line for the enhanced editor (50 lines)
     From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
   • Re: Equivalent of "top" command in command line for the enhanced editor (60 lines)
     From: Francis Dwyer <franwdwyer@GOOGLEMAIL.COM>

10. Error trying to establish ODBC connection between SAS and SQL Server
    • Re: Error trying to establish ODBC connection between SAS and SQL Server (110 lines)
      From: Irin later <irinfigvam@YAHOO.COM>

11. File Upload Interface on SAS Report Delivery Portal
    • File Upload Interface on SAS Report Delivery Portal (15 lines)
      From: Lokraj Adhikari <lokraj.adhikari@AUSTINCC.EDU>

12. Find department with most employees
    • Find department with most employees (51 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Find department with most employees (74 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Find department with most employees (86 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Find department with most employees (94 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Find department with most employees (86 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: Find department with most employees (93 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Find department with most employees (90 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Find department with most employees (108 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Find department with most employees (121 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: Find department with most employees (125 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Find department with most employees (138 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Find department with most employees (88 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

13. Friday humor (on Wed) (statistics)
    • Friday humor (on Wed) (statistics) (20 lines)
      From: Joe Kelley <jkelley@UGA.EDU>
    • Re: Friday humor (on Wed) (statistics) (46 lines)
      From: Raymond Liedka <liedka@OAKLAND.EDU>
    • Re: Friday humor (on Wed) (statistics) (32 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Friday humor (on Wed) (statistics) (37 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: Friday humor (on Wed) (statistics) (77 lines)
      From: Burton, John (CONT) <John.Burton@CAPITALONE.COM>
    • Re: Friday humor (on Wed) (statistics) (86 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Friday humor (on Wed) (statistics) (39 lines)
      From: DUELL, BOB <bd9439@ATT.COM>

14. Fwd: Question For The Financially Astute
    • Fwd: Question For The Financially Astute (56 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

15. GLIMMIX - Standardized Residuals
    • GLIMMIX - Standardized Residuals (25 lines)
      From: R B <ryan.andrew.black@GMAIL.COM>
    • Re: GLIMMIX - Standardized Residuals (43 lines)
      From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>
    • Re: GLIMMIX - Standardized Residuals (52 lines)
      From: R B <ryan.andrew.black@GMAIL.COM>

16. GML in SAS and R
    • Re: GML in SAS and R (167 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Re: GML in SAS and R (146 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: GML in SAS and R (163 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

17. Global Assessment of Functioning?
    • Global Assessment of Functioning? (33 lines)
      From: Dennis G. Fisher, Ph.D. <dfisher@CSULB.EDU>

18. Help in destringing mult vars then recoding into new indicator vars
    • Help in destringing mult vars then recoding into new indicator vars (21 lines)
      From: Alison <alisontetler@YAHOO.COM>
    • Re: Help in destringing mult vars then recoding into new indicator vars (81 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

19. Inserting Values
    • Inserting Values (60 lines)
      From: Randy <randistan69@HOTMAIL.COM>
    • Re: Inserting Values (101 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: Inserting Values (147 lines)
      From: Randy <randistan69@HOTMAIL.COM>
    • Re: Inserting Values (172 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Inserting Values (105 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: Inserting Values (134 lines)
      From: Randy <randistan69@HOTMAIL.COM>
    • Re: Inserting Values (159 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: Inserting Values (141 lines)
      From: SUBSCRIBE SAS-L Anonymous <randistan69@HOTMAIL.COM>
    • Re: Inserting Values (64 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Inserting Values (94 lines)
      From: Randy <randistan69@HOTMAIL.COM>
    • Re: Inserting Values (185 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: Inserting Values (57 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>

20. Lagging Groups
    • Re: Lagging Groups (51 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>

21. Linux rbrowser in multiuser environment
    • Linux rbrowser in multiuser environment (24 lines)
      From: Byron Kirby <byronkirby@GMAIL.COM>

22. List of Variables through empty PDV
    • List of Variables through empty PDV (41 lines)
      From: Dan Abner <dan.abner99@GMAIL.COM>
    • Re: List of Variables through empty PDV (61 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: List of Variables through empty PDV (54 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: List of Variables through empty PDV (78 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: List of Variables through empty PDV (43 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

23. Lost Card Question
    • Lost Card Question (51 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Lost Card Question (74 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>

24. Lost Card Question (please see this one)
    • Lost Card Question (please see this one) (51 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Lost Card Question (please see this one) (64 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>
    • Re: Lost Card Question (please see this one) (58 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Lost Card Question (please see this one) (74 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Lost Card Question (please see this one) (96 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Lost Card Question (please see this one) (107 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Lost Card Question (please see this one) (121 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

25. ODS HTML "Relative" paths
    • ODS HTML "Relative" paths (52 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>

26. ODS HTML tagset: Freeze column and scroll
    • ODS HTML tagset: Freeze column and scroll (67 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: ODS HTML tagset: Freeze column and scroll (23 lines)
      From: Subhadra Srigiriraju <subhadrasri@GMAIL.COM>
    • Re: ODS HTML tagset: Freeze column and scroll (115 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: ODS HTML tagset: Freeze column and scroll (44 lines)
      From: Subhadra Srigiriraju <subhadrasri@GMAIL.COM>
    • Re: ODS HTML tagset: Freeze column and scroll (200 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>

27. OT: Modifying SAS Explorer's view in Excel
    • OT: Modifying SAS Explorer's view in Excel (58 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: OT: Modifying SAS Explorer's view in Excel (88 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: OT: Modifying SAS Explorer's view in Excel (102 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

28. Old data rescue (French CLOTILDE software)
    • Old data rescue (French CLOTILDE software) (20 lines)
      From: flavigny <flavigny@FREE.FR>

29. Passing a variable value as condition into a where clause
    • Passing a variable value as condition into a where clause (39 lines)
      From: Fernando Tenorio <fetcs74@GMAIL.COM>
    • Re: Passing a variable value as condition into a where clause (105 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: Passing a variable value as condition into a where clause (85 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: Passing a variable value as condition into a where clause (73 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Passing a variable value as condition into a where clause (17 lines)
      From: Fernando Tenorio <fetcs74@GMAIL.COM>
    • Re: Passing a variable value as condition into a where clause (84 lines)
      From: Fernando Tenorio <fetcs74@GMAIL.COM>
    • Re: Passing a variable value as condition into a where clause (118 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Passing a variable value as condition into a where clause (51 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Passing a variable value as condition into a where clause (125 lines)
      From: Fernando Tenorio <fetcs74@GMAIL.COM>
    • Re: Passing a variable value as condition into a where clause (12 lines)
      From: Fernando Tenorio <fetcs74@GMAIL.COM>

30. Random Intercept and Slope Models
    • Random Intercept and Slope Models (26 lines)
      From: Amir Kasaeian <amir_kasaeian@YAHOO.COM>

31. Reshape data so that each category becomes a new variable
    • Reshape data so that each category becomes a new variable (31 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: Reshape data so that each category becomes a new variable (72 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Reshape data so that each category becomes a new variable (38 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Reshape data so that each category becomes a new variable (68 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Reshape data so that each category becomes a new variable (82 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: Reshape data so that each category becomes a new variable (16 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: Reshape data so that each category becomes a new variable (99 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: Reshape data so that each category becomes a new variable (69 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: Reshape data so that each category becomes a new variable (26 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: Reshape data so that each category becomes a new variable (26 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: Reshape data so that each category becomes a new variable (68 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Reshape data so that each category becomes a new variable (50 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: Reshape data so that each category becomes a new variable (52 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Reshape data so that each category becomes a new variable (55 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Reshape data so that each category becomes a new variable (38 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: Reshape data so that each category becomes a new variable (58 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Reshape data so that each category becomes a new variable (63 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

32. SAS Job (10-12 hours with good hourly rate)
    • SAS Job (10-12 hours with good hourly rate) (16 lines)
      From: Sadaf Raique <xeeshannshk@GMAIL.COM>

33. SAS Job (only for 10-12 hours)
    • SAS Job (only for 10-12 hours) (19 lines)
      From: Zeeshan Shaikh <xeeshannshk@GMAIL.COM>

34. SAS is recognizing dataasets on one computer and not another
    • SAS is recognizing dataasets on one computer and not another (27 lines)
      From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU>
    • Re: SAS is recognizing dataasets on one computer and not another (44 lines)
      From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU>
    • Re: SAS is recognizing dataasets on one computer and not another (66 lines)
      From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU>
    • Re: SAS is recognizing dataasets on one computer and not another (44 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: SAS is recognizing dataasets on one computer and not another (92 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: SAS is recognizing dataasets on one computer and not another (44 lines)
      From: Venky Chakravarthy <sasyellvenky@GMAIL.COM>

35. SPDS Table:Locale Error
    • SPDS Table:Locale Error (32 lines)
      From: Ravinder Maramamula <ravinsun@GMAIL.COM>

36. Sgdesign
    • Sgdesign (14 lines)
      From: Stephane COLAS <scolas@DATAMETRIC.FR>
    • Re: Sgdesign (12 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: Sgdesign (45 lines)
      From: Stephane COLAS <scolas@DATAMETRIC.FR>
    • Re: Sgdesign (45 lines)
      From: Stephane COLAS <scolas@DATAMETRIC.FR>
    • Re: Sgdesign (16 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: Sgdesign (24 lines)
      From: Stephane COLAS <scolas@DATAMETRIC.FR>
    • Re: Sgdesign (19 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: Sgdesign (13 lines)
      From: Stephane COLAS <scolas@DATAMETRIC.FR>
    • Re: Sgdesign (11 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: Sgdesign (12 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>

37. Special Characters
    • Special Characters (41 lines)
      From: Singh <adsingh78@GMAIL.COM>
    • Re: Special Characters (108 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>
    • Re: Special Characters (51 lines)
      From: Venky Chakravarthy <sasyellvenky@GMAIL.COM>
    • Re: Special Characters (69 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Special Characters (90 lines)
      From: Venky Chakravarthy <sasyellvenky@GMAIL.COM>
    • Re: Special Characters (55 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>

38. Systematic Jittering?
    • Systematic Jittering? (31 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Systematic Jittering? (69 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Systematic Jittering? (78 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Systematic Jittering? (24 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Systematic Jittering? (35 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Systematic Jittering? (91 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Systematic Jittering? (145 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Systematic Jittering? (17 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>

39. Trend Analysis in Proportions using NLMIXED
    • Trend Analysis in Proportions using NLMIXED (39 lines)
      From: R B <ryan.andrew.black@GMAIL.COM>
    • Re: Trend Analysis in Proportions using NLMIXED (91 lines)
      From: Robin R High <rhigh@UNMC.EDU>
    • Re: Trend Analysis in Proportions using NLMIXED (103 lines)
      From: R B <ryan.andrew.black@GMAIL.COM>
    • Re: Trend Analysis in Proportions using NLMIXED (122 lines)
      From: R B <ryan.andrew.black@GMAIL.COM>
    • Re: Trend Analysis in Proportions using NLMIXED (143 lines)
      From: Robin R High <rhigh@UNMC.EDU>
    • Re: Trend Analysis in Proportions using NLMIXED (159 lines)
      From: Robin R High <rhigh@UNMC.EDU>
    • Re: Trend Analysis in Proportions using NLMIXED (187 lines)
      From: R B <ryan.andrew.black@GMAIL.COM>
    • Re: Trend Analysis in Proportions using NLMIXED (220 lines)
      From: Robin R High <rhigh@UNMC.EDU>

40. Trend in Proportions via NLMIXED (A Simulation Experiment)
    • Trend in Proportions via NLMIXED (A Simulation Experiment) (127 lines)
      From: R B <ryan.andrew.black@GMAIL.COM>
    • Re: Trend in Proportions via NLMIXED (A Simulation Experiment) (183 lines)
      From: Viel, Kevin <kviel@SJHA.ORG>

41. WPS
    • WPS (12 lines)
      From: E P <evp_sasl@YAHOO.CA>
    • Re: WPS (20 lines)
      From: Phil Rack <philrack@MINEQUEST.COM>

42. Wide CI but good power?
    • Wide CI but good power? (29 lines)
      From: Jan McClure <mc006@PACBELL.NET>
    • Re: Wide CI but good power? (59 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Wide CI but good power? (63 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: Wide CI but good power? (84 lines)
      From: Robin R High <rhigh@UNMC.EDU>

43. an issue in 9.3 sgplot -loess
    • Re: an issue in 9.3 sgplot -loess (26 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: an issue in 9.3 sgplot -loess (16 lines)
      From: SUBSCRIBE SAS-L JingJu11 S <jingju11@HOTMAIL.COM>

44. auto-scheduling a program to run
    • auto-scheduling a program to run (29 lines)
      From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US>
    • Re: auto-scheduling a program to run (26 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: auto-scheduling a program to run (119 lines)
      From: Michael Davis <michael@BASSETTCONSULTING.COM>
    • Re: auto-scheduling a program to run (62 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: auto-scheduling a program to run (13 lines)
      From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US>

45. comparison of proportions
    • comparison of proportions (19 lines)
      From: christine <christinepeloquin1@GMAIL.COM>
    • Re: comparison of proportions (39 lines)
      From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>

46. connecting to SQL Server / connection=shared
    • connecting to SQL Server / connection=shared (37 lines)
      From: Miller, Jeremy T. (CDC/OSELS/PHSPO) <zyp9@CDC.GOV>

47. most efficient way to connect to sql server from sas
    • most efficient way to connect to sql server from sas (26 lines)
      From: AnnHett <annhett@GMAIL.COM>
    • Re: most efficient way to connect to sql server from sas (45 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: most efficient way to connect to sql server from sas (50 lines)
      From: AnnHett <annhett@GMAIL.COM>
    • Re: most efficient way to connect to sql server from sas (76 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: most efficient way to connect to sql server from sas (60 lines)
      From: AnnHett <annhett@GMAIL.COM>
    • Re: most efficient way to connect to sql server from sas (63 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: most efficient way to connect to sql server from sas (19 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: most efficient way to connect to sql server from sas (49 lines)
      From: AnnHett <annhett@GMAIL.COM>

48. need helps for data mamipulation
    • Re: need helps for data mamipulation (115 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: need helps for data mamipulation (122 lines)
      From: joe zhou <g75wez1@GMAIL.COM>
    • Re: need helps for data mamipulation (167 lines)
      From: Venky Chakravarthy <sasyellvenky@GMAIL.COM>

49. ods/pdf anchor, can it be done with BY processing?
    • ods/pdf anchor, can it be done with BY processing? (19 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>

50. proc report and row color
    • proc report and row color (23 lines)
      From: Masoud Pajoh <mpajoh@ODOT.ORG>
    • Re: proc report and row color (88 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
    • Re: proc report and row color (114 lines)
      From: Masoud Pajoh <mpajoh@ODOT.ORG>
    • Re: proc report and row color (169 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
    • Re: proc report and row color (211 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>

51. question for MIANALYZE
    • question for MIANALYZE (32 lines)
      From: df ss <tggsun@YAHOO.COM>

52. question for users of R+SAS
    • Re: question for users of R+SAS (73 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: question for users of R+SAS (38 lines)
      From: Jerry Davis <jwd@UGA.EDU>
    • Re: question for users of R+SAS (78 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: question for users of R+SAS (24 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: question for users of R+SAS (39 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: question for users of R+SAS (42 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: question for users of R+SAS (58 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>

53. quick ata step
    • quick ata step (21 lines)
      From: hua gang <hg448@YAHOO.COM>
    • Re: quick ata step (54 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: quick ata step (59 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

54. reading a comma *.csv file, convert it to a flat file, scale from 0-5 to 1-6 and blanks to be spaces.
    • Re: reading a comma *.csv file, convert it to a flat file, scale from 0-5 to 1-6 and blanks to be spaces. (127 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: reading a comma *.csv file, convert it to a flat file, scale from 0-5 to 1-6 and blanks to be spaces. (116 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: reading a comma *.csv file, convert it to a flat file, scale from 0-5 to 1-6 and blanks to be spaces. (119 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>

55. something interesting about INFILE and SET statements
    • something interesting about INFILE and SET statements (71 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: something interesting about INFILE and SET statements (75 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: something interesting about INFILE and SET statements (145 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

56. special character
    • special character (28 lines)
      From: WIELKI Andre <wielki@INED.FR>

57. unsubscribe
    • unsubscribe (12 lines)
      From: rajat kapoor <rajatkapoor87@GMAIL.COM>
    • Re: unsubscribe (32 lines)
      From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>