Table of contents:

• "Row title space too small to print titles for the table statement" error (4 messages)
• $90 discount if you register for Clinical Trial Analysis Using R before June 17th
• A Format quesion - Urgent (2 messages)
• AW: Thursday Theory
• An average question (4 messages)
• Automatic reply: SAS-L Digest - 10 Jun 2011 - Special issue (#2011-589) (4 messages)
• Automatic reply: SAS-L Digest - 13 Jun 2011 to 14 Jun 2011 - Special issue (#2011-599)
• Automatic reply: [SAS-L] PROC SGPLOT graphs not opening
• Automatic reply: why we need "stop;" preceding "run;" ?
• Automatische Antwort: proc report
• Best practices question: connecting to Oracle databases via SAS
• Bootstrap Logistic Regression (2 messages)
• CSV file problem
• Can one determine pixel length of a string? (7 messages)
• Chance to Make SAS-L History: Did You Know That... (7 messages)
• Connect Local SAS to a SAS Server (2 messages)
• Exporting Facilities with Macro
• FICO Webinar: Boost Insurance Underwriting Accuracy with Predictive Analytics
• GLIMMIX LSMEANS PLOT: WANT A common y axis with by statement (2 messages)
• General math-ish type help - PCA and Cluster Analysis (2 messages)
• Help in SAS- Insurance Domain (2 messages)
• Historical note - Univac 1 (7 messages)
• How to Add Prior Month Totals in PROC REPORT (2 messages)
• How to model this?
• INPUT oddity (4 messages)
• IS8601TM (14 messages)
• Long text fields in Excel
• Macro to write to external file (19 messages)
• OT, UE to find Unicode: 0x0 ?
• OT: Friday Humor
• OT: Thursday Theory
• Online Summer Courses Using R Software
• PROC SGPLOT graphs not opening
• Proc datasets and Oracle error (4 messages)
• Random coefficient mixed model (2 messages)
• Request
• SAS 9.3? (4 messages)
• SAS IML Error: Segmentation Violation In Task [ IML (2) ]
• SAS OR and ETS (5 messages)
• SAS connection to SQL Server (2 messages)
• SAS report to Web and Web query to SAS
• SAS tip: SAS name literal variable names as argument (2 messages)
• Sas Date Conversion (11 messages)
• Starting Display Manager in 9.2
• Strange symbol in SAS editor (5 messages)
• Thursday Theory
• Validating multiple date formats and SAS test data entry (2 messages)
• automatically collect all variable names of a data set (5 messages)
• calling WinZip to zip output data from a SAS program (2 messages)
• censored independent variable? (4 messages)
• creating Stored Process in Base SAS and EG and how to connect SP to IDP (2 messages)
• hard-coded hash object, what's wrong?
• import then export but get different result?? (4 messages)
• locking issues with view (3 messages)
• ods
• problems with locks on stored macros
• proc report (4 messages)
• quiet install
• quotation doubled when exporting? (4 messages)
• row-level vs column-level SUM in proc sql (5 messages)
• scanning a set of variables (8 messages)
• tukey test (2 messages)
• type conversion; was: between operation
• why we need "stop;" preceding "run;" ? (7 messages)

1. "Row title space too small to print titles for the table statement" error
   • "Row title space too small to print titles for the table statement" error (66 lines)
     From: White, Svend A. <SvendW@HEALTH.OK.GOV>
   • Re: "Row title space too small to print titles for the table statement" error (74 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: "Row title space too small to print titles for the table statement" error (101 lines)
     From: White, Svend A. <SvendW@HEALTH.OK.GOV>
   • Re: "Row title space too small to print titles for the table statement" error (103 lines)
     From: White, Svend A. <SvendW@HEALTH.OK.GOV>

2. $90 discount if you register for Clinical Trial Analysis Using R before June 17th
   • $90 discount if you register for Clinical Trial Analysis Using R before June 17th (398 lines)
     From: Dorothy Middleton <courses@STATCOURSE.COM>

3. A Format quesion - Urgent
   • A Format quesion - Urgent (24 lines)
     From: Tom Smith <need_sas_help@YAHOO.COM>
   • Re: A Format quesion - Urgent (35 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>

4. AW: Thursday Theory
   • AW: Thursday Theory (126 lines)
     From: Olaf Kruse <olaf.kruse@VST-GMBH.DE>

5. An average question
   • An average question (20 lines)
     From: Morley Herbert <Morley.Herbert@HCAHEALTHCARE.COM>
   • Re: An average question (39 lines)
     From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
   • Re: An average question (36 lines)
     From: Steve Denham <stevedrd@YAHOO.COM>
   • Re: An average question (64 lines)
     From: Søren Lassen <s.lassen@POST.TELE.DK>

6. Automatic reply: SAS-L Digest - 10 Jun 2011 - Special issue (#2011-589)
   • Automatic reply: SAS-L Digest - 10 Jun 2011 - Special issue (#2011-589) (15 lines)
     From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU>
   • Automatic reply: SAS-L Digest - 10 Jun 2011 - Special issue (#2011-589) (21 lines)
     From: Carol Olson <Carol.Olson@MEREDITH.COM>
   • Re: Automatic reply: SAS-L Digest - 10 Jun 2011 - Special issue (#2011-589) (28 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>
   • Re: Automatic reply: SAS-L Digest - 10 Jun 2011 - Special issue (#2011-589) (36 lines)
     From: F J Kelley <jkelley@UGA.EDU>

7. Automatic reply: SAS-L Digest - 13 Jun 2011 to 14 Jun 2011 - Special issue (#2011-599)
   • Automatic reply: SAS-L Digest - 13 Jun 2011 to 14 Jun 2011 - Special issue (#2011-599) (12 lines)
     From: Erika Steinmetz <esteinmetz@AAMC.ORG>

8. Automatic reply: [SAS-L] PROC SGPLOT graphs not opening
   • Automatic reply: [SAS-L] PROC SGPLOT graphs not opening (21 lines)
     From: Aminova, Frida <faminova@PACE.EDU>

9. Automatic reply: why we need "stop;" preceding "run;" ?
   • Automatic reply: why we need "stop;" preceding "run;" ? (19 lines)
     From: Jan Squillace <Jan.Squillace@SAS.COM>

10. Automatische Antwort: proc report
    • Automatische Antwort: proc report (15 lines)
      From: Sascha Räuschel <Sascha.Raeuschel@GER.SAS.COM>

11. Best practices question: connecting to Oracle databases via SAS
    • Re: Best practices question: connecting to Oracle databases via SAS (86 lines)
      From: Muhammad Sohail <sohailbme@GMAIL.COM>

12. Bootstrap Logistic Regression
    • Bootstrap Logistic Regression (44 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>
    • Re: Bootstrap Logistic Regression (36 lines)
      From: R B <ryan.andrew.black@GMAIL.COM>

13. CSV file problem
    • Re: CSV file problem (65 lines)
      From: =?utf-8?B?15LXk9eZINeR158g15DXkdeZ?= <GADI_B@MALAM.COM>

14. Can one determine pixel length of a string?
    • Can one determine pixel length of a string? (12 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Can one determine pixel length of a string? (25 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Can one determine pixel length of a string? (35 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Can one determine pixel length of a string? (63 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Can one determine pixel length of a string? (86 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Can one determine pixel length of a string? (116 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Can one determine pixel length of a string? (148 lines)
      From: Murphy Choy <goladin@GMAIL.COM>

15. Chance to Make SAS-L History: Did You Know That...
    • Re: Chance to Make SAS-L History: Did You Know That... (110 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Chance to Make SAS-L History: Did You Know That... (103 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Chance to Make SAS-L History: Did You Know That... (126 lines)
      From: Bolotin Yevgeniy <ybolotin@SCHOOLS.NYC.GOV>
    • Re: Chance to Make SAS-L History: Did You Know That... (130 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: Chance to Make SAS-L History: Did You Know That... (25 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Chance to Make SAS-L History: Did You Know That... (76 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Chance to Make SAS-L History: Did You Know That... (135 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

16. Connect Local SAS to a SAS Server
    • Connect Local SAS to a SAS Server (44 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>
    • Re: Connect Local SAS to a SAS Server (71 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

17. Exporting Facilities with Macro
    • Re: Exporting Facilities with Macro (12 lines)
      From: Kim Brown <kibrown@LADHS.ORG>

18. FICO Webinar: Boost Insurance Underwriting Accuracy with Predictive Analytics
    • FICO Webinar: Boost Insurance Underwriting Accuracy with Predictive Analytics (39 lines)
      From: Vincent Granville <vincentg@DATASHAPING.COM>

19. GLIMMIX LSMEANS PLOT: WANT A common y axis with by statement
    • GLIMMIX LSMEANS PLOT: WANT A common y axis with by statement (87 lines)
      From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU>
    • Re: GLIMMIX LSMEANS PLOT: WANT A common y axis with by statement (37 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

20. General math-ish type help - PCA and Cluster Analysis
    • General math-ish type help - PCA and Cluster Analysis (21 lines)
      From: Chris Bat <darth.pathos@GMAIL.COM>
    • Re: General math-ish type help - PCA and Cluster Analysis (39 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

21. Help in SAS- Insurance Domain
    • Help in SAS- Insurance Domain (13 lines)
      From: Vishali Rajiv <vishalirajiv@YAHOO.COM>
    • Re: Help in SAS- Insurance Domain (23 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

22. Historical note - Univac 1
    • Historical note - Univac 1 (16 lines)
      From: Hoyle, Larry <larryhoyle@KU.EDU>
    • Re: Historical note - Univac 1 (40 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: Historical note - Univac 1 (57 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Historical note - Univac 1 (60 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Historical note - Univac 1 (66 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: Historical note - Univac 1 (117 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Historical note - Univac 1 (129 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

23. How to Add Prior Month Totals in PROC REPORT
    • How to Add Prior Month Totals in PROC REPORT (27 lines)
      From: jack quin <qinlixun@GMAIL.COM>
    • Re: How to Add Prior Month Totals in PROC REPORT (39 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

24. How to model this?
    • How to model this? (23 lines)
      From: Sphinx Verdant <verdantsphinx@GMAIL.COM>

25. INPUT oddity
    • INPUT oddity (42 lines)
      From: Jeff J. Voeller <SAS-Programmer@WYWH.COM>
    • Re: INPUT oddity (54 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: INPUT oddity (25 lines)
      From: Jeff J. Voeller <SAS-Programmer@WYWH.COM>
    • Re: INPUT oddity (44 lines)
      From: Ben <benpub7@YAHOO.COM>

26. IS8601TM
    • IS8601TM (31 lines)
      From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM>
    • Re: IS8601TM (42 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: IS8601TM (72 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: IS8601TM (80 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: IS8601TM (13 lines)
      From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM>
    • Re: IS8601TM (20 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: IS8601TM (137 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: IS8601TM (34 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: IS8601TM (150 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: IS8601TM (166 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: IS8601TM (53 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: IS8601TM (88 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: IS8601TM (60 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: IS8601TM (102 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

27. Long text fields in Excel
    • Re: Long text fields in Excel (143 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>

28. Macro to write to external file
    • Macro to write to external file (37 lines)
      From: SUBSCRIBE SAS-L Joe H. Smith <peesari.mahesh@GMAIL.COM>
    • Re: Macro to write to external file (79 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Macro to write to external file (58 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Macro to write to external file (116 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Macro to write to external file (97 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Macro to write to external file (110 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Macro to write to external file (147 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Macro to write to external file (196 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Macro to write to external file (225 lines)
      From: MAHESH <peesari.mahesh@GMAIL.COM>
    • Re: Macro to write to external file (243 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Macro to write to external file (80 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Macro to write to external file (243 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Macro to write to external file (261 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Macro to write to external file (252 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Macro to write to external file (277 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Macro to write to external file (265 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Macro to write to external file (294 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Macro to write to external file (311 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Macro to write to external file (18 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

29. OT, UE to find Unicode: 0x0 ?
    • OT, UE to find Unicode: 0x0 ? (17 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>

30. OT: Friday Humor
    • OT: Friday Humor (20 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

31. OT: Thursday Theory
    • OT: Thursday Theory (87 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

32. Online Summer Courses Using R Software
    • Online Summer Courses Using R Software (71 lines)
      From: Geoffrey Hubona <ghubona@GMAIL.COM>

33. PROC SGPLOT graphs not opening
    • PROC SGPLOT graphs not opening (26 lines)
      From: Chris Bat <darth.pathos@GMAIL.COM>

34. Proc datasets and Oracle error
    • Proc datasets and Oracle error (48 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Proc datasets and Oracle error (80 lines)
      From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM>
    • Re: Proc datasets and Oracle error (99 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Proc datasets and Oracle error (127 lines)
      From: Carol Bristow <Carol.Bristow@DPRA.COM>

35. Random coefficient mixed model
    • Random coefficient mixed model (22 lines)
      From: Sphinx Verdant <verdantsphinx@GMAIL.COM>
    • Re: Random coefficient mixed model (48 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

36. Request
    • Re: Request (69 lines)
      From: Vishali Rajiv <vishalirajiv@YAHOO.COM>

37. SAS 9.3?
    • SAS 9.3? (12 lines)
      From: F J Kelley <jkelley@UGA.EDU>
    • Re: SAS 9.3? (28 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: SAS 9.3? (38 lines)
      From: F J Kelley <jkelley@UGA.EDU>
    • Re: SAS 9.3? (35 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>

38. SAS IML Error: Segmentation Violation In Task [ IML (2) ]
    • SAS IML Error: Segmentation Violation In Task [ IML (2) ] (59 lines)
      From: Robert Feyerharm <rfeyerha@TRAVELERS.COM>

39. SAS OR and ETS
    • Re: SAS OR and ETS (76 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: SAS OR and ETS (22 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: SAS OR and ETS (37 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: SAS OR and ETS (48 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: SAS OR and ETS (50 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

40. SAS connection to SQL Server
    • SAS connection to SQL Server (26 lines)
      From: Gordon Keeler <gkeeler@PSYCH.DUHS.DUKE.EDU>
    • Re: SAS connection to SQL Server (39 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

41. SAS report to Web and Web query to SAS
    • Re: SAS report to Web and Web query to SAS (60 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

42. SAS tip: SAS name literal variable names as argument
    • SAS tip: SAS name literal variable names as argument (69 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>
    • Re: SAS tip: SAS name literal variable names as argument (100 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

43. Sas Date Conversion
    • Sas Date Conversion (43 lines)
      From: Adams, Nicholas <NRAdams@CVTY.COM>
    • Re: Sas Date Conversion (87 lines)
      From: Jack Clark <jclark@HILLTOP.UMBC.EDU>
    • Re: Sas Date Conversion (54 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Sas Date Conversion (79 lines)
      From: Adams, Nicholas <NRAdams@CVTY.COM>
    • Re: Sas Date Conversion (69 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Sas Date Conversion (61 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Sas Date Conversion (77 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Sas Date Conversion (88 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Sas Date Conversion (50 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: Sas Date Conversion (32 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Sas Date Conversion (37 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

44. Starting Display Manager in 9.2
    • Starting Display Manager in 9.2 (33 lines)
      From: Joe DeShon <joedeshon@COMCAST.NET>

45. Strange symbol in SAS editor
    • Strange symbol in SAS editor (20 lines)
      From: John Hendrickx <john2.hendrickx@GMAIL.COM>
    • Re: Strange symbol in SAS editor (32 lines)
      From: Ben <benpub7@YAHOO.COM>
    • Re: Strange symbol in SAS editor (63 lines)
      From: John Hendrickx <john2.hendrickx@GMAIL.COM>
    • Re: Strange symbol in SAS editor (87 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Strange symbol in SAS editor (40 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

46. Thursday Theory
    • Re: Thursday Theory (154 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

47. Validating multiple date formats and SAS test data entry
    • Validating multiple date formats and SAS test data entry (36 lines)
      From: Brian Wallace <brian_c_wallace@YAHOO.COM>
    • Re: Validating multiple date formats and SAS test data entry (91 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

48. automatically collect all variable names of a data set
    • automatically collect all variable names of a data set (19 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: automatically collect all variable names of a data set (40 lines)
      From: John Hendrickx <john2.hendrickx@GMAIL.COM>
    • Re: automatically collect all variable names of a data set (40 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: automatically collect all variable names of a data set (27 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: automatically collect all variable names of a data set (27 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

49. calling WinZip to zip output data from a SAS program
    • calling WinZip to zip output data from a SAS program (39 lines)
      From: Burton, Ray <Ray.Burton@ACS-INC.COM>
    • Re: calling WinZip to zip output data from a SAS program (51 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

50. censored independent variable?
    • censored independent variable? (11 lines)
      From: Xin Wei <xinwei@STAT.PSU.EDU>
    • Re: censored independent variable? (37 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: censored independent variable? (50 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: censored independent variable? (50 lines)
      From: Xin Wei <xinwei@STAT.PSU.EDU>

51. creating Stored Process in Base SAS and EG and how to connect SP to IDP
    • creating Stored Process in Base SAS and EG and how to connect SP to IDP (19 lines)
      From: Pradeep <chittiprolupradeep@GMAIL.COM>
    • Re: creating Stored Process in Base SAS and EG and how to connect SP to IDP (42 lines)
      From: Murphy Choy <goladin@GMAIL.COM>

52. hard-coded hash object, what's wrong?
    • Re: hard-coded hash object, what's wrong? (346 lines)
      From: Scott Bass <sas_l_739@YAHOO.COM.AU>

53. import then export but get different result??
    • import then export but get different result?? (161 lines)
      From: Alex Tang <Alex.Tang@CREDITONE.COM>
    • Re: import then export but get different result?? (229 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: import then export but get different result?? (194 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: import then export but get different result?? (240 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

54. locking issues with view
    • Re: locking issues with view (31 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: locking issues with view (36 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: locking issues with view (59 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

55. ods
    • ods (30 lines)
      From: Huaandrew <andrew0845@HOTMAIL.COM>

56. problems with locks on stored macros
    • problems with locks on stored macros (31 lines)
      From: White, Svend A. <SvendW@HEALTH.OK.GOV>

57. proc report
    • proc report (105 lines)
      From: John Mike <sasslick@GMAIL.COM>
    • Re: proc report (118 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: proc report (128 lines)
      From: John Mike <sasslick@GMAIL.COM>
    • Re: proc report (121 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>

58. quiet install
    • quiet install (34 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

59. quotation doubled when exporting?
    • quotation doubled when exporting? (71 lines)
      From: Alex Tang <Alex.Tang@CREDITONE.COM>
    • Re: quotation doubled when exporting? (92 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: quotation doubled when exporting? (104 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: quotation doubled when exporting? (167 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

60. row-level vs column-level SUM in proc sql
    • row-level vs column-level SUM in proc sql (50 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: row-level vs column-level SUM in proc sql (56 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: row-level vs column-level SUM in proc sql (69 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: row-level vs column-level SUM in proc sql (88 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: row-level vs column-level SUM in proc sql (96 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

61. scanning a set of variables
    • scanning a set of variables (49 lines)
      From: Sally Vegso <Sally.Vegso@YALE.EDU>
    • Re: scanning a set of variables (12 lines)
      From: Gabriel Rosas <rosas.gabe@GMAIL.COM>
    • Re: scanning a set of variables (43 lines)
      From: Sally Vegso <Sally.Vegso@YALE.EDU>
    • Re: scanning a set of variables (14 lines)
      From: Gabriel Rosas <rosas.gabe@GMAIL.COM>
    • Re: scanning a set of variables (75 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: scanning a set of variables (110 lines)
      From: Sally Vegso <Sally.Vegso@YALE.EDU>
    • Re: scanning a set of variables (84 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: scanning a set of variables (40 lines)
      From: Sally Vegso <Sally.Vegso@YALE.EDU>

62. tukey test
    • tukey test (84 lines)
      From: Johanna Griffin <jkgriffin@UCDAVIS.EDU>
    • Re: tukey test (48 lines)
      From: Jerry Davis <jwd@UGA.EDU>

63. type conversion; was: between operation
    • Re: type conversion; was: between operation (53 lines)
      From: Jim Groeneveld <jim.1stat@YAHOO.COM>

64. why we need "stop;" preceding "run;" ?
    • why we need "stop;" preceding "run;" ? (41 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: why we need "stop;" preceding "run;" ? (79 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: why we need "stop;" preceding "run;" ? (74 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: why we need "stop;" preceding "run;" ? (56 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: why we need "stop;" preceding "run;" ? (86 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: why we need "stop;" preceding "run;" ? (107 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: why we need "stop;" preceding "run;" ? (133 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>