Table of contents:

• About SAS 64 bit: A note of caution, with the hope SAS Institute will fix such problems: (3 messages)
• Activate First Worksheet in Excel Workbook Using DDE Command (was Autosize Excel Columns from SAS) (5 messages)
• Alternative for "goto" in do loop (37 messages)
• Autosize Excel Columns from SAS (3 messages)
• Can specify one column when importing excel file? (2 messages)
• Code Challenge: matching names (3 messages)
• Creating a Dataset (4 messages)
• DI Studio algorithm to derive optimal hashexp value (5 messages)
• Data import from Excel (8 messages)
• Data manipulation help (2 messages)
• Date lookup
• Distinguishing between duplicates and missing lookups with set-key
• FORMAT? (2 messages)
• FW: Autosize Excel Columns from SAS
• FW: Word dde and apostrophe
• Fastest way to merge large dataset
• Import when only first comma is delimiter (5 messages)
• Interesting statistical modeling question - PROC MIXED? Time series? (8 messages)
• NYTimes.com: New Setback in Attempt to Contain the Gulf Oil Spill
• Need a shell script to run the SAS Jobs (5 messages)
• New Google Wonder Wheel Search Aid
• New SAS e-Guide: Quick Results with Proc SQL (4 messages)
• ODBC Connection Problem (3 messages)
• Off To See The Doc Sunshine (2 messages)
• Only able to edit in FSView
• PROC FORMAT & PROC GPLOT (4 messages)
• PROC G3D: Rotate graph (3 messages)
• PROC MEANS output data set order (3 messages)
• Please help: Need a shell script to run the SAS Jobs:
• Proc GMAP legend level? (2 messages)
• Proc Gplot - Scaling of x-axis (4 messages)
• Proc Report Header (2 messages)
• Proc Sort with 0 Input Observations (3 messages)
• R, SAS, SPSS and Open Source
• Reg: FORMAT? (3 messages)
• Remote submit macro-generated code (2 messages)
• Retain -- Data Structure
• Ross Ihaka's reflections on the future of R computing....
• Running SAS batch programs asynchronously (4 messages)
• SAS AF and Xwindows (Vista) (3 messages)
• SAS Enterprise: Suppress ODS output for some procs but not others (6 messages)
• SAS code to validate email Id (4 messages)
• SAS insufficient memory (2 messages)
• SESUG Early Conference Registration Now Open
• SG Procedures (7 messages)
• SGPlot (2 messages)
• SGPlot Quest - seeking help (2 messages)
• Simple ANOVA, R different from SAS? (6 messages)
• Smaller server for SAS at a hospital (2 messages)
• Specifying var format in proc import (3 messages)
• Statistical reasoning and modeling (3 messages)
• Stupid Human Do-Loop Trick (6 messages)
• Subscripts in SAS, not in RTF or HTML (2 messages)
• Subset a dataset using a Categorical variable
• URGENT: SAS Enterprise Graph Output GPATH (2 messages)
• Zero-Inflated Gamma = Hurdle Gamma? (10 messages)
• bold font for multiple rows in PROC Report
• calculating predicted probabilities in logistic regression
• create a WORKSHEET with a space in the sheet name
• dataset already open for output (4 messages)
• excelxp tagset/proc report and (not) skipping lines (4 messages)
• exporting more than 65000rows to Excel (6 messages)
• how to use wildcards here? (7 messages)
• how to write the model statements in proc mixed for a repeated measures (2 messages)
• news: SAP buys Sybase
• proc g3d: Reverse Axis (6 messages)
• question about stepwise multivariate analysis of variance (stepwise MANOVA) (7 messages)
• sas enumeration? (6 messages)
• splitting terms from one macro argument (6 messages)
• two Proc Report/RTF questions (3 messages)
• varying symbol markers in ODS graphics

1. About SAS 64 bit: A note of caution, with the hope SAS Institute will fix such problems:
   • Re: About SAS 64 bit: A note of caution, with the hope SAS Institute will fix such problems: (52 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>
   • Re: About SAS 64 bit: A note of caution, with the hope SAS Institute will fix such problems: (68 lines)
     From: Dale McLerran <stringplayer_2@YAHOO.COM>
   • Re: About SAS 64 bit: A note of caution, with the hope SAS Institute will fix such problems: (40 lines)
     From: Kevin Viel <citam.sasl@GMAIL.COM>

2. Activate First Worksheet in Excel Workbook Using DDE Command (was Autosize Excel Columns from SAS)
   • Re: Activate First Worksheet in Excel Workbook Using DDE Command (was Autosize Excel Columns from SAS) (292 lines)
     From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
   • Re: Activate First Worksheet in Excel Workbook Using DDE Command (was Autosize Excel Columns from SAS) (43 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: Activate First Worksheet in Excel Workbook Using DDE Command (was Autosize Excel Columns from SAS) (267 lines)
     From: Jack Clark <jclark@HILLTOP.UMBC.EDU>
   • Re: Activate First Worksheet in Excel Workbook Using DDE Command (was Autosize Excel Columns from SAS) (214 lines)
     From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
   • Activate First Worksheet in Excel Workbook Using DDE Command (was Autosize Excel Columns from SAS) (196 lines)
     From: Jack Clark <jclark@HILLTOP.UMBC.EDU>

3. Alternative for "goto" in do loop
   • Re: Alternative for "goto" in do loop (290 lines)
     From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
   • Re: Alternative for "goto" in do loop (229 lines)
     From: Paul Dorfman <sashole@BELLSOUTH.NET>
   • Re: Alternative for "goto" in do loop (211 lines)
     From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
   • Re: Alternative for "goto" in do loop (239 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: Alternative for "goto" in do loop (176 lines)
     From: Paul Dorfman <sashole@BELLSOUTH.NET>
   • Re: Alternative for "goto" in do loop (204 lines)
     From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
   • Re: Alternative for "goto" in do loop (149 lines)
     From: Sid N <nsid31@GMAIL.COM>
   • Re: Alternative for "goto" in do loop (127 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: Alternative for "goto" in do loop (78 lines)
     From: Søren Lassen <s.lassen@POST.TELE.DK>
   • Re: Alternative for "goto" in do loop (86 lines)
     From: Mary <mlhoward@AVALON.NET>
   • Re: Alternative for "goto" in do loop (42 lines)
     From: Lex Jansen <spam@LEXJANSEN.COM>
   • Re: Alternative for "goto" in do loop (69 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: Alternative for "goto" in do loop (27 lines)
     From: Søren Lassen <s.lassen@POST.TELE.DK>
   • Re: Alternative for "goto" in do loop (126 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: Alternative for "goto" in do loop (386 lines)
     From: Søren Lassen <s.lassen@POST.TELE.DK>
   • Re: Alternative for "goto" in do loop (31 lines)
     From: Chang Chung <chang_y_chung@HOTMAIL.COM>
   • Re: Alternative for "goto" in do loop (116 lines)
     From: Anderson, James <James.Anderson@UCSF.EDU>
   • Re: Alternative for "goto" in do loop (27 lines)
     From: Chang Chung <chang_y_chung@HOTMAIL.COM>
   • Re: Alternative for "goto" in do loop (131 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: Alternative for "goto" in do loop (121 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: Alternative for "goto" in do loop (131 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: Alternative for "goto" in do loop (110 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: Alternative for "goto" in do loop (88 lines)
     From: Chang Chung <chang_y_chung@HOTMAIL.COM>
   • Re: Alternative for "goto" in do loop (98 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: Alternative for "goto" in do loop (54 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>
   • Re: Alternative for "goto" in do loop (285 lines)
     From: Anderson, James <James.Anderson@UCSF.EDU>
   • Re: Alternative for "goto" in do loop (275 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>
   • Re: Alternative for "goto" in do loop (220 lines)
     From: Søren Lassen <s.lassen@POST.TELE.DK>
   • Re: Alternative for "goto" in do loop (85 lines)
     From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>
   • Re: Alternative for "goto" in do loop (158 lines)
     From: Chang Chung <chang_y_chung@HOTMAIL.COM>
   • Re: Alternative for "goto" in do loop (72 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: Alternative for "goto" in do loop (71 lines)
     From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
   • Re: Alternative for "goto" in do loop (71 lines)
     From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
   • Re: Alternative for "goto" in do loop (94 lines)
     From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
   • Re: Alternative for "goto" in do loop (96 lines)
     From: Alan Churchill <alan.churchill@SAVIAN.NET>
   • Re: Alternative for "goto" in do loop (79 lines)
     From: Murphy Choy <goladin@GMAIL.COM>
   • Alternative for "goto" in do loop (53 lines)
     From: Sid N <nsid31@GMAIL.COM>

4. Autosize Excel Columns from SAS
   • Re: Autosize Excel Columns from SAS (117 lines)
     From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
   • Re: Autosize Excel Columns from SAS (85 lines)
     From: Ken Borowiak <evilpettingzoo97@AOL.COM>
   • Autosize Excel Columns from SAS (64 lines)
     From: Jack Clark <jclark@HILLTOP.UMBC.EDU>

5. Can specify one column when importing excel file?
   • Re: Can specify one column when importing excel file? (52 lines)
     From: Nat Wooding <nathani@VERIZON.NET>
   • Re: Can specify one column when importing excel file? (34 lines)
     From: Arthur Tabachneck <art297@NETSCAPE.NET>

6. Code Challenge: matching names
   • Re: Code Challenge: matching names (82 lines)
     From: Chang Chung <chang_y_chung@HOTMAIL.COM>
   • Re: Code Challenge: matching names (48 lines)
     From: Sterling Paramore <gnilrets@GMAIL.COM>
   • Code Challenge: matching names (35 lines)
     From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>

7. Creating a Dataset
   • Re: Creating a Dataset (100 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: Creating a Dataset (91 lines)
     From: Bradley J. Heins <hein0106@UMN.EDU>
   • Re: Creating a Dataset (75 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Creating a Dataset (44 lines)
     From: Brad Heins <hein0106@UMN.EDU>

8. DI Studio algorithm to derive optimal hashexp value
   • Re: DI Studio algorithm to derive optimal hashexp value (460 lines)
     From: Paul Dorfman <sashole@BELLSOUTH.NET>
   • Re: DI Studio algorithm to derive optimal hashexp value (419 lines)
     From: Scott Bass <sas_l_739@YAHOO.COM.AU>
   • Re: DI Studio algorithm to derive optimal hashexp value (87 lines)
     From: Paul Dorfman <sashole@BELLSOUTH.NET>
   • Re: DI Studio algorithm to derive optimal hashexp value (251 lines)
     From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
   • DI Studio algorithm to derive optimal hashexp value (25 lines)
     From: Scott Bass <sas_l_739@YAHOO.COM.AU>

9. Data import from Excel
   • Re: Data import from Excel (60 lines)
     From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
   • Re: Data import from Excel (28 lines)
     From: r.hockey@SPH.UQ.EDU.AU
   • Re: Data import from Excel (24 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: Data import from Excel (12 lines)
     From: Mark S. <marksmolkin@GMAIL.COM>
   • Re: Data import from Excel (35 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: Data import from Excel (13 lines)
     From: Mark S. <marksmolkin@GMAIL.COM>
   • Re: Data import from Excel (26 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Data import from Excel (17 lines)
     From: Mark S. <marksmolkin@GMAIL.COM>

10. Data manipulation help
    • Re: Data manipulation help (148 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>
    • Data manipulation help (126 lines)
      From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU>

11. Date lookup
    • Re: Date lookup (151 lines)
      From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>

12. Distinguishing between duplicates and missing lookups with set-key
    • Re: Distinguishing between duplicates and missing lookups with set-key (56 lines)
      From: Kevin Viel <citam.sasl@GMAIL.COM>

13. FORMAT?
    • Re: FORMAT? (34 lines)
      From: nadeene.blanchard@ONTARIO.CA
    • Re: FORMAT? (60 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>

14. FW: Autosize Excel Columns from SAS
    • FW: Autosize Excel Columns from SAS (106 lines)
      From: Sudo Ku <crafty876@HOTMAIL.COM>

15. FW: Word dde and apostrophe
    • Re: FW: Word dde and apostrophe (57 lines)
      From: Kevin Viel <citam.sasl@GMAIL.COM>

16. Fastest way to merge large dataset
    • Re: Fastest way to merge large dataset (299 lines)
      From: Aldi <aldi@WUSTL.EDU>

17. Import when only first comma is delimiter
    • Re: Import when only first comma is delimiter (57 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Import when only first comma is delimiter (127 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Import when only first comma is delimiter (50 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Import when only first comma is delimiter (78 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Import when only first comma is delimiter (44 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>

18. Interesting statistical modeling question - PROC MIXED? Time series?
    • Re: Interesting statistical modeling question - PROC MIXED? Time series? (27 lines)
      From: Kevin Viel <citam.sasl@GMAIL.COM>
    • Re: Interesting statistical modeling question - PROC MIXED? Time series? (162 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Interesting statistical modeling question - PROC MIXED? Time series? (149 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: Interesting statistical modeling question - PROC MIXED? Time series? (133 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Interesting statistical modeling question - PROC MIXED? Time series? (97 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: Interesting statistical modeling question - PROC MIXED? Time series? (56 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: Interesting statistical modeling question - PROC MIXED? Time series? (71 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Interesting statistical modeling question - PROC MIXED? Time series? (44 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

19. NYTimes.com: New Setback in Attempt to Contain the Gulf Oil Spill
    • NYTimes.com: New Setback in Attempt to Contain the Gulf Oil Spill (32 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

20. Need a shell script to run the SAS Jobs
    • Re: Need a shell script to run the SAS Jobs (38 lines)
      From: MichelleZ <michelle_zunnurain@HOTMAIL.COM>
    • Re: Need a shell script to run the SAS Jobs (118 lines)
      From: Michelle Zunnurain <michelle_zunnurain@HOTMAIL.COM>
    • Re: Need a shell script to run the SAS Jobs (83 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
    • Re: Need a shell script to run the SAS Jobs (35 lines)
      From: MichelleZ <michelle_zunnurain@HOTMAIL.COM>
    • Re: Need a shell script to run the SAS Jobs (21 lines)
      From: MichelleZ <michelle_zunnurain@HOTMAIL.COM>

21. New Google Wonder Wheel Search Aid
    • New Google Wonder Wheel Search Aid (9 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

22. New SAS e-Guide: Quick Results with Proc SQL
    • Re: New SAS e-Guide: Quick Results with Proc SQL (62 lines)
      From: shyamprasad samisetti <shyam.cbz@GMAIL.COM>
    • Re: New SAS e-Guide: Quick Results with Proc SQL (71 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: New SAS e-Guide: Quick Results with Proc SQL (52 lines)
      From: Andre Wielki <wielki@INED.FR>
    • New SAS e-Guide: Quick Results with Proc SQL (48 lines)
      From: Sunil Gupta <sunil@GUPTAPROGRAMMING.COM>

23. ODBC Connection Problem
    • Re: ODBC Connection Problem (48 lines)
      From: Craig Johnson <cjohns38@GMAIL.COM>
    • Re: ODBC Connection Problem (38 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>
    • ODBC Connection Problem (19 lines)
      From: Craig Johnson <cjohns38@GMAIL.COM>

24. Off To See The Doc Sunshine
    • Re: Off To See The Doc Sunshine (27 lines)
      From: Toby Dunn <tobydunn@HOTMAIL.COM>
    • Off To See The Doc Sunshine (26 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>

25. Only able to edit in FSView
    • Only able to edit in FSView (15 lines)
      From: Craig Johnson <cjohns38@GMAIL.COM>

26. PROC FORMAT & PROC GPLOT
    • Re: PROC FORMAT & PROC GPLOT (112 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: PROC FORMAT & PROC GPLOT (67 lines)
      From: OR Stats <stats112@GMAIL.COM>
    • Re: PROC FORMAT & PROC GPLOT (58 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • PROC FORMAT & PROC GPLOT (33 lines)
      From: OR Stats <stats112@GMAIL.COM>

27. PROC G3D: Rotate graph
    • Re: PROC G3D: Rotate graph (34 lines)
      From: OR Stats <stats112@GMAIL.COM>
    • Re: PROC G3D: Rotate graph (26 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • PROC G3D: Rotate graph (12 lines)
      From: OR Stats <stats112@GMAIL.COM>

28. PROC MEANS output data set order
    • Re: PROC MEANS output data set order (177 lines)
      From: Jack Clark <jclark@HILLTOP.UMBC.EDU>
    • Re: PROC MEANS output data set order (150 lines)
      From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>
    • PROC MEANS output data set order (112 lines)
      From: Lorne Klassen <lk1@ROGERS.COM>

29. Please help: Need a shell script to run the SAS Jobs:
    • Re: Please help: Need a shell script to run the SAS Jobs: (183 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

30. Proc GMAP legend level?
    • Re: Proc GMAP legend level? (68 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Proc GMAP legend level? (51 lines)
      From: Sarah Cox <saslearner2006@GMAIL.COM>

31. Proc Gplot - Scaling of x-axis
    • Re: Proc Gplot - Scaling of x-axis (139 lines)
      From: Mike Zdeb <msz03@ALBANY.EDU>
    • Re: Proc Gplot - Scaling of x-axis (64 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Proc Gplot - Scaling of x-axis (83 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Proc Gplot - Scaling of x-axis (53 lines)
      From: Deep <adsingh78@GMAIL.COM>

32. Proc Report Header
    • Re: Proc Report Header (77 lines)
      From: Ken Borowiak <evilpettingzoo97@AOL.COM>
    • Proc Report Header (35 lines)
      From: Ken Barz <zrab123@COMCAST.NET>

33. Proc Sort with 0 Input Observations
    • Re: Proc Sort with 0 Input Observations (50 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: Proc Sort with 0 Input Observations (58 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Proc Sort with 0 Input Observations (19 lines)
      From: Amy Adyanthaya <amy.adyanthaya@MPI.COM>

34. R, SAS, SPSS and Open Source
    • R, SAS, SPSS and Open Source (42 lines)
      From: Philip Rack <PhilRack@MINEQUEST.COM>

35. Reg: FORMAT?
    • Re: Reg: FORMAT? (54 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Reg: FORMAT? (81 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Reg: FORMAT? (50 lines)
      From: amit kumar <amitsasbi@GMAIL.COM>

36. Remote submit macro-generated code
    • Re: Remote submit macro-generated code (40 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Remote submit macro-generated code (27 lines)
      From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM>

37. Retain -- Data Structure
    • Re: Retain -- Data Structure (82 lines)
      From: Richard A. DeVenezia <rdevenezia@GMAIL.COM>

38. Ross Ihaka's reflections on the future of R computing....
    • Ross Ihaka's reflections on the future of R computing.... (30 lines)
      From: xin <xinwei@STAT.PSU.EDU>

39. Running SAS batch programs asynchronously
    • Re: Running SAS batch programs asynchronously (664 lines)
      From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>
    • Re: Running SAS batch programs asynchronously (566 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: Running SAS batch programs asynchronously (25 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Running SAS batch programs asynchronously (520 lines)
      From: Scott Bass <sas_l_739@YAHOO.COM.AU>

40. SAS AF and Xwindows (Vista)
    • Re: SAS AF and Xwindows (Vista) (19 lines)
      From: Dianne Rhodes <diannerhodes@COMCAST.NET>
    • Re: SAS AF and Xwindows (Vista) (36 lines)
      From: Graham Murray <graham.murray@WEBMINER.CO.UK>
    • SAS AF and Xwindows (Vista) (19 lines)
      From: Norman Weston <nweston@AMGEN.COM>

41. SAS Enterprise: Suppress ODS output for some procs but not others
    • Re: SAS Enterprise: Suppress ODS output for some procs but not others (106 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: SAS Enterprise: Suppress ODS output for some procs but not others (102 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: SAS Enterprise: Suppress ODS output for some procs but not others (111 lines)
      From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>
    • Re: SAS Enterprise: Suppress ODS output for some procs but not others (59 lines)
      From: OR Stats <stats112@GMAIL.COM>
    • Re: SAS Enterprise: Suppress ODS output for some procs but not others (51 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • SAS Enterprise: Suppress ODS output for some procs but not others (36 lines)
      From: OR Stats <stats112@GMAIL.COM>

42. SAS code to validate email Id
    • Re: SAS code to validate email Id (54 lines)
      From: manish kumar <man13ish@GMAIL.COM>
    • Re: SAS code to validate email Id (35 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: SAS code to validate email Id (49 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • SAS code to validate email Id (43 lines)
      From: manish kumar <man13ish@GMAIL.COM>

43. SAS insufficient memory
    • Re: SAS insufficient memory (58 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>
    • SAS insufficient memory (47 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>

44. SESUG Early Conference Registration Now Open
    • SESUG Early Conference Registration Now Open (32 lines)
      From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>

45. SG Procedures
    • Re: SG Procedures (65 lines)
      From: Huang, Ya <Ya.Huang@AMYLIN.COM>
    • Re: SG Procedures (78 lines)
      From: Huang, Ya <Ya.Huang@AMYLIN.COM>
    • Re: SG Procedures (43 lines)
      From: Hixon, John <jhixon@AMGEN.COM>
    • Re: SG Procedures (59 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: SG Procedures (141 lines)
      From: Huang, Ya <Ya.Huang@AMYLIN.COM>
    • Re: SG Procedures (87 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • SG Procedures (48 lines)
      From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM>

46. SGPlot
    • Re: SGPlot (28 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>
    • SGPlot (16 lines)
      From: Ken Barz <zrab123@COMCAST.NET>

47. SGPlot Quest - seeking help
    • Re: SGPlot Quest - seeking help (76 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • SGPlot Quest - seeking help (48 lines)
      From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM>

48. Simple ANOVA, R different from SAS?
    • Re: Simple ANOVA, R different from SAS? (125 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Simple ANOVA, R different from SAS? (68 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Simple ANOVA, R different from SAS? (83 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: Simple ANOVA, R different from SAS? (111 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Simple ANOVA, R different from SAS? (48 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Simple ANOVA, R different from SAS? (41 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>

49. Smaller server for SAS at a hospital
    • Re: Smaller server for SAS at a hospital (45 lines)
      From: Scott Czepiel <sczepiel@GMAIL.COM>
    • Smaller server for SAS at a hospital (20 lines)
      From: Kevin Viel <citam.sasl@GMAIL.COM>

50. Specifying var format in proc import
    • Re: Specifying var format in proc import (111 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Specifying var format in proc import (66 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Specifying var format in proc import (46 lines)
      From: HealthMaps <healthmaps@COMCAST.NET>

51. Statistical reasoning and modeling
    • Re: Statistical reasoning and modeling (30 lines)
      From: Kevin Viel <citam.sasl@GMAIL.COM>
    • Re: Statistical reasoning and modeling (35 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Statistical reasoning and modeling (21 lines)
      From: sudip chatterjee <sudip.memphis@GMAIL.COM>

52. Stupid Human Do-Loop Trick
    • Re: Stupid Human Do-Loop Trick (32 lines)
      From: Kevin Viel <citam.sasl@GMAIL.COM>
    • Re: Stupid Human Do-Loop Trick (62 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Stupid Human Do-Loop Trick (46 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Stupid Human Do-Loop Trick (91 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: Stupid Human Do-Loop Trick (61 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Stupid Human Do-Loop Trick (102 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

53. Subscripts in SAS, not in RTF or HTML
    • Re: Subscripts in SAS, not in RTF or HTML (63 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>
    • Subscripts in SAS, not in RTF or HTML (38 lines)
      From: Uddin, Sharif [ATRMUS] <SUddin@ITS.JNJ.COM>

54. Subset a dataset using a Categorical variable
    • Re: Subset a dataset using a Categorical variable (153 lines)
      From: Craig Johnson <cjohns38@GMAIL.COM>

55. URGENT: SAS Enterprise Graph Output GPATH
    • Re: URGENT: SAS Enterprise Graph Output GPATH (66 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • URGENT: SAS Enterprise Graph Output GPATH (28 lines)
      From: OR Stats <stats112@GMAIL.COM>

56. Zero-Inflated Gamma = Hurdle Gamma?
    • Re: Zero-Inflated Gamma = Hurdle Gamma? (66 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: Zero-Inflated Gamma = Hurdle Gamma? (53 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: Zero-Inflated Gamma = Hurdle Gamma? (38 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: Zero-Inflated Gamma = Hurdle Gamma? (97 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: Zero-Inflated Gamma = Hurdle Gamma? (100 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Zero-Inflated Gamma = Hurdle Gamma? (79 lines)
      From: Ryan Black <ryan.andrew.black@GMAIL.COM>
    • Re: Zero-Inflated Gamma = Hurdle Gamma? (60 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: Zero-Inflated Gamma = Hurdle Gamma? (40 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: Zero-Inflated Gamma = Hurdle Gamma? (46 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Zero-Inflated Gamma = Hurdle Gamma? (22 lines)
      From: Ryan Black <ryan.andrew.black@GMAIL.COM>

57. bold font for multiple rows in PROC Report
    • bold font for multiple rows in PROC Report (41 lines)
      From: Karalee Poschman <kposchman@YAHOO.COM>

58. calculating predicted probabilities in logistic regression
    • calculating predicted probabilities in logistic regression (45 lines)
      From: Robert Feyerharm <robertf@HEALTH.OK.GOV>

59. create a WORKSHEET with a space in the sheet name
    • Re: create a WORKSHEET with a space in the sheet name (179 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

60. dataset already open for output
    • Re: dataset already open for output (43 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: dataset already open for output (41 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: dataset already open for output (46 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • dataset already open for output (36 lines)
      From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU>

61. excelxp tagset/proc report and (not) skipping lines
    • Re: excelxp tagset/proc report and (not) skipping lines (217 lines)
      From: Sudo Ku <crafty876@HOTMAIL.COM>
    • Re: excelxp tagset/proc report and (not) skipping lines (103 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: excelxp tagset/proc report and (not) skipping lines (94 lines)
      From: Sudo Ku <crafty876@HOTMAIL.COM>
    • excelxp tagset/proc report and (not) skipping lines (39 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

62. exporting more than 65000rows to Excel
    • Re: exporting more than 65000rows to Excel (61 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: exporting more than 65000rows to Excel (49 lines)
      From: Tom Quin <tomquin99@GMAIL.COM>
    • Re: exporting more than 65000rows to Excel (128 lines)
      From: Yusuf Mohamedshah <zulsdad@GMAIL.COM>
    • Re: exporting more than 65000rows to Excel (67 lines)
      From: Alan Churchill <alan.churchill@SAVIAN.NET>
    • Re: exporting more than 65000rows to Excel (40 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • exporting more than 65000rows to Excel (17 lines)
      From: Tom Smith <tomquin99@GMAIL.COM>

63. how to use wildcards here?
    • Re: how to use wildcards here? (60 lines)
      From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>
    • Re: how to use wildcards here? (50 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: how to use wildcards here? (44 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: how to use wildcards here? (52 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: how to use wildcards here? (40 lines)
      From: Jeff <zhujp98@GMAIL.COM>
    • Re: how to use wildcards here? (31 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • how to use wildcards here? (17 lines)
      From: Jeff <zhujp98@GMAIL.COM>

64. how to write the model statements in proc mixed for a repeated measures
    • Re: how to write the model statements in proc mixed for a repeated measures (66 lines)
      From: Steve Denham <stevedrd@YAHOO.COM>
    • how to write the model statements in proc mixed for a repeated measures (23 lines)
      From: Xin Wei <xinwei@STAT.PSU.EDU>

65. news: SAP buys Sybase
    • news: SAP buys Sybase (24 lines)
      From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>

66. proc g3d: Reverse Axis
    • Re: proc g3d: Reverse Axis (92 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: proc g3d: Reverse Axis (68 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: proc g3d: Reverse Axis (104 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: proc g3d: Reverse Axis (42 lines)
      From: OR Stats <stats112@GMAIL.COM>
    • Re: proc g3d: Reverse Axis (27 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • proc g3d: Reverse Axis (10 lines)
      From: OR Stats <stats112@GMAIL.COM>

67. question about stepwise multivariate analysis of variance (stepwise MANOVA)
    • Re: question about stepwise multivariate analysis of variance (stepwise MANOVA) (29 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: question about stepwise multivariate analysis of variance (stepwise MANOVA) (23 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: question about stepwise multivariate analysis of variance (stepwise MANOVA) (87 lines)
      From: Philip Rack <PhilRack@MINEQUEST.COM>
    • Re: question about stepwise multivariate analysis of variance (stepwise MANOVA) (79 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: question about stepwise multivariate analysis of variance (stepwise MANOVA) (57 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: question about stepwise multivariate analysis of variance (stepwise MANOVA) (41 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • question about stepwise multivariate analysis of variance (stepwise MANOVA) (18 lines)
      From: 126@agri521 <agri521@126.COM>

68. sas enumeration?
    • Re: sas enumeration? (88 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: sas enumeration? (68 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: sas enumeration? (87 lines)
      From: OVIDIU NEGRILA <diddy1512@YAHOO.COM>
    • Re: sas enumeration? (51 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: sas enumeration? (45 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • sas enumeration? (29 lines)
      From: Dave Smith <daveyboysmith_123@YAHOO.COM>

69. splitting terms from one macro argument
    • Re: splitting terms from one macro argument (180 lines)
      From: Ian Whitlock <iw1sas@GMAIL.COM>
    • Re: splitting terms from one macro argument (98 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: splitting terms from one macro argument (38 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: splitting terms from one macro argument (47 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: splitting terms from one macro argument (98 lines)
      From: Fehd, Ronald J. (CDC/OSELS/NCPHI) <rjf2@CDC.GOV>
    • splitting terms from one macro argument (61 lines)
      From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>

70. two Proc Report/RTF questions
    • Re: two Proc Report/RTF questions (44 lines)
      From: KarlK <karlstudboy@HOTMAIL.COM>
    • Re: two Proc Report/RTF questions (144 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • two Proc Report/RTF questions (118 lines)
      From: Treder, David <dtreder@GENESEEISD.ORG>

71. varying symbol markers in ODS graphics
    • varying symbol markers in ODS graphics (16 lines)
      From: Ben Fertig <bfertig@UMCES.EDU>