Table of contents:

• 72 Processors, 48GB --> $15,000 (3 messages)
• A question about bootstrap (2 messages)
• A question about proc sql
• Any hardware gurus? SAS config question (9 messages)
• Applications of "SAS Variable Lists".
• Automated Installation of Enterprise Guide 1.3
• Automatically outputing the results of a PROC FREQ (6 messages)
• Can Jmp be a client of SAS/connect server?
• Collapsing data..
• Concatenation of character values by groups of observations (6 messages)
• Conditionally writing code (7 messages)
• Consultant Need for 4 weeks project
• Count number of linefeeds - resolved
• Count number of linefeeds in a file (4 messages)
• Create a table with the 4 most recent news items (4 messages)
• Creating Multiple datasets (2 messages)
• Data input error inside macro (6 messages)
• Data management question (3 messages)
• Data manipulation question (6 messages)
• Dirty Datasets from Another OS (2 messages)
• Do you prefer Proc Report or Proc Tabulate?Ans,If proc report,Would you Please explain? (2 messages)
• ERROR 22-322: Syntax error, expecting one of the following: a name, _ALL_, _CHARACTER_, (4 messages)
• ERROR: Subquery evaluated to more than one row
• Enterprise miner and SAS Code (3 messages)
• Expanding a dataset through the merge statement
• Extracting data out of a messy text file (6 messages)
• FW: SAS-callable Sudaan v9.0.1 and SAS v9.2
• FYI: book review of interest to MIXED fans
• GMAP/ Zip code shape file (3 messages)
• HASH objects in future releases (3 messages)
• How does SAS find Ridge Regression RMSE?
• How to Transpose Single Column (2 messages)
• How to change Partial dates to Numeric (7 messages)
• How to put macro do-loop code into a macro variable? (21 messages)
• I Want to Stop Hard-Coding Dates (5 messages)
• I get to correct Dale!!! (2 messages)
• Import Multiple Excel sheets using dde and macro (6 messages)
• Importing mixed datatype fields into SAS
• Infile doesn't read in all records
• Is SQL plenty good enough for complex data transformation? (3 messages)
• LARS (Efron et 2004) and SAS (3 messages)
• Libname Macro (4 messages)
• Loading SAS Data Set To Oracle Error (4 messages)
• Log error with PROC MIANALYZE
• Looking for Distributors/Importers: Pocket Size Welding Machine (2 messages)
• Looping Macro Vairables
• Macro question (10 messages)
• Merging datasets
• Missing values....
• Multiple tables next to each other Excel
• NESUG Follow-up: comments on the search facility in the new SAS tech support page
• Need Help with SAS Code! 1978 Harrison and Rubinfield Problem! (2 messages)
• New Job : SAS Programmers USA ( East Coast ) , willing to Sponsor non US Citizens
• New Job: Senior Contract Biostatistician USA, Will Sponsor non USA Citizens
• New Jobs in USA
• New PROC REPORT conundrum (2 messages)
• ODBC -> MySQL db doesn't get WHERE clause? (5 messages)
• ODS the Easy Way -- A Tutorial
• OT: good code snippet manager (2 messages)
• OUTPUT WITH SURVEYMEANS/FREQ
• Optimisation - SAS OR
• PharmaSUG 2008 - Call For Papers
• Proc Format Error (22 messages)
• Proc SQl does double EXCEPT?? (2 messages)
• Regarding finding Oct Nov Dec Values.
• Regarding populating values
• Reminder: PharmaSUG 2008 - Call For Papers
• Renaming the column lables (4 messages)
• SAS --> Excel
• SAS 8.2 not support vista operating system
• SAS Error Message (3 messages)
• SAS-L Digest - 17 Nov 2007 - Special issue (#2007-1901)
• SAS-L post not going to COMP.SOFT-SYS.SAS (2 messages)
• SAS/AF -- Frame within a Frame (4 messages)
• SQL Create table vs SET DATAFILE (5 messages)
• SQL Cross Join using a data step
• SQL or SAS or Neither? (2 messages)
• SQl Error message (6 messages)
• SVM in SAS : Using Soft-Margin ?
• Solving integrals (5 messages)
• Starting Values (2 messages)
• Strong Variable Level Encryption (6 messages)
• Transforming negative variable (26 messages)
• Tricky Retain Step (7 messages)
• Using IML for pdf and cdf contaminated normal (13 messages)
• Visualizing Change - White Paper, Webcast, Flash Demo Available
• What simple tutorials do you need for Base SAS? (9 messages)
• Which Kind of Conjoint Analysis Can I Use?
• Which type of the Conjoint Analysis is it? (2 messages)
• Windows vs. Linux Performance (3 messages)
• [WEB/AF ECLIPSE] Tableview Editable
• any way to sort large table faster than proc sort? (17 messages)
• change format of a variable (7 messages)
• column to row conversion (2 messages)
• compute SEP from survival data
• convert real binary to hex representation, result is out of expectation. (5 messages)
• count distinct userid using proc sql
• create matrix like table without IML (2 messages)
• creating data table from many tables (5 messages)
• data management (2 messages)
• informats reading NUMERIC data (4 messages)
• inserting values into macro variable using array (5 messages)
• little library (4 messages)
• look for better codes than mine (6 messages)
• optimisation (2 messages)
• recover the number of observations of the tables of a library
• reference code in another sas program (8 messages)
• regarding outputdatasets
• remove the proc title from standard output listing (2 messages)
• repeating a procedure on a number of variables (4 messages)
• run same program on multiple files (6 messages)
• run same program on multiple files-2 (2 messages)
• sas.com community newsletters
• second test post from SAS-L
• second test post to comp.soft-sys.sas sent via Google Groups
• smallest positive number? (4 messages)
• suggestions with papers on problems of stepwise reg with existence of collinearity (4 messages)
• test post sent from SAS-L
• test post to comp.soft-sys.sas sent via Google groups
• time data into a SAS time format (3 messages)
• title question. (2 messages)
• transform data (12 messages)
• work space on mainframe (3 messages)
• x command to run acrobat distiller, but won't exit after finishing (5 messages)

1. 72 Processors, 48GB --> $15,000
   • 72 Processors, 48GB --> $15,000 (62 lines)
     From: Alan Churchill <savian001@GMAIL.COM>
   • Re: 72 Processors, 48GB --> $15,000 (10 lines)
     From: ben.powell@CLA.CO.UK
   • Re: 72 Processors, 48GB --> $15,000 (26 lines)
     From: Chang Chung <chang_y_chung@HOTMAIL.COM>

2. A question about bootstrap
   • A question about bootstrap (29 lines)
     From: Hassan Eini <einizinab@GMAIL.COM>
   • Re: A question about bootstrap (46 lines)
     From: data _null_, <datanull@GMAIL.COM>

3. A question about proc sql
   • A question about proc sql (31 lines)
     From: Yufei Wang <yufeiw@GMAIL.COM>

4. Any hardware gurus? SAS config question
   • Re: Any hardware gurus? SAS config question (47 lines)
     From: kubert <kurt.bremser@ALLIANZ.AT>
   • Re: Any hardware gurus? SAS config question (18 lines)
     From: Patrick <patrick.matter@GMX.CH>
   • Re: Any hardware gurus? SAS config question (23 lines)
     From: kubert <kurt.bremser@ALLIANZ.AT>
   • Any hardware gurus? SAS config question (29 lines)
     From: Floyd Moseby <floydmoseby@GMAIL.COM>
   • Re: Any hardware gurus? SAS config question (63 lines)
     From: Alan Churchill <savian001@GMAIL.COM>
   • Re: Any hardware gurus? SAS config question (17 lines)
     From: Floyd Moseby <floydmoseby@GMAIL.COM>
   • Re: Any hardware gurus? SAS config question (35 lines)
     From: Alan Churchill <savian001@GMAIL.COM>
   • Re: Any hardware gurus? SAS config question (39 lines)
     From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
   • Re: Any hardware gurus? SAS config question (52 lines)
     From: kubert <kurt.bremser@ALLIANZ.AT>

5. Applications of "SAS Variable Lists".
   • Applications of "SAS Variable Lists". (23 lines)
     From: OCDS <OuachitaClinicalDataServices@GMAIL.COM>

6. Automated Installation of Enterprise Guide 1.3
   • Automated Installation of Enterprise Guide 1.3 (14 lines)
     From: kubert <kurt.bremser@ALLIANZ.AT>

7. Automatically outputing the results of a PROC FREQ
   • Automatically outputing the results of a PROC FREQ (16 lines)
     From: Syb it <sas_datalover@YAHOO.COM>
   • Re: Automatically outputing the results of a PROC FREQ (75 lines)
     From: Jack Clark <JClark@CHPDM.UMBC.EDU>
   • Re: Automatically outputing the results of a PROC FREQ (93 lines)
     From: Syb it <sas_datalover@YAHOO.COM>
   • Re: Automatically outputing the results of a PROC FREQ (233 lines)
     From: Jack Clark <JClark@CHPDM.UMBC.EDU>
   • Re: Automatically outputing the results of a PROC FREQ (240 lines)
     From: Syb it <sas_datalover@YAHOO.COM>
   • Re: Automatically outputing the results of a PROC FREQ (415 lines)
     From: Long, Stuart (NIH/NIEHS) [C] <long3@NIEHS.NIH.GOV>

8. Can Jmp be a client of SAS/connect server?
   • Can Jmp be a client of SAS/connect server? (23 lines)
     From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

9. Collapsing data..
   • Collapsing data.. (46 lines)
     From: souga soga <souga1234@GMAIL.COM>

10. Concatenation of character values by groups of observations
    • Concatenation of character values by groups of observations (49 lines)
      From: Laurenz Trawnicek <laurenz.trawnicek@OCTAPHARMA.AT>
    • Re: Concatenation of character values by groups of observations (56 lines)
      From: Gina Nicolosi <ginanicolosi@HOTMAIL.COM>
    • Re: Concatenation of character values by groups of observations (116 lines)
      From: Ed Heaton <EdHeaton@WESTAT.COM>
    • Re: Concatenation of character values by groups of observations (9 lines)
      From: Gina Nicolosi <ginanicolosi@HOTMAIL.COM>
    • Re: Concatenation of character values by groups of observations (22 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: Concatenation of character values by groups of observations (14 lines)
      From: Laurenz Trawnicek <laurenz.trawnicek@OCTAPHARMA.AT>

11. Conditionally writing code
    • Conditionally writing code (35 lines)
      From: Paul <psquares@YAHOO.COM.AU>
    • Re: Conditionally writing code (84 lines)
      From: Tom Hide <tom.hide@DEHIWORLD.COM>
    • Re: Conditionally writing code (62 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Conditionally writing code (73 lines)
      From: Paul <psquares@YAHOO.COM.AU>
    • Re: Conditionally writing code (91 lines)
      From: Tom Hide <tom.hide@DEHIWORLD.COM>
    • Re: Conditionally writing code (20 lines)
      From: Paul Pham <psquares@YAHOO.COM.AU>
    • Re: Conditionally writing code (16 lines)
      From: Paul <psquares@YAHOO.COM.AU>

12. Consultant Need for 4 weeks project
    • Consultant Need for 4 weeks project (18 lines)
      From: Alejandro Jaramillo <info@DATAMEANS.COM>

13. Count number of linefeeds - resolved
    • Count number of linefeeds - resolved (29 lines)
      From: Bob_Abelson@HGSI.COM

14. Count number of linefeeds in a file
    • Count number of linefeeds in a file (23 lines)
      From: Bob_Abelson@HGSI.COM
    • Re: Count number of linefeeds in a file (70 lines)
      From: Jack Clark <JClark@CHPDM.UMBC.EDU>
    • Re: Count number of linefeeds in a file (63 lines)
      From: Ian Whitlock <iw1junk@COMCAST.NET>
    • Re: Count number of linefeeds in a file (56 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>

15. Create a table with the 4 most recent news items
    • Create a table with the 4 most recent news items (63 lines)
      From: KatieGwaith@GOOGLEMAIL.COM
    • Re: Create a table with the 4 most recent news items (67 lines)
      From: KatieGwaith@GOOGLEMAIL.COM
    • Re: Create a table with the 4 most recent news items (69 lines)
      From: KatieGwaith@GOOGLEMAIL.COM
    • Re: Create a table with the 4 most recent news items (116 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>

16. Creating Multiple datasets
    • Creating Multiple datasets (20 lines)
      From: yogi <yogibad@GMAIL.COM>
    • Re: Creating Multiple datasets (37 lines)
      From: Tree Frog <tree.frog2@HOTMAIL.COM>

17. Data input error inside macro
    • Data input error inside macro (86 lines)
      From: Surajit Das <surajit.das@DECIDYN.COM>
    • Re: Data input error inside macro (91 lines)
      From: Anindya Mozumdar <anindya.lugbang@GMAIL.COM>
    • Re: Data input error inside macro (21 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Data input error inside macro (105 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: Data input error inside macro (48 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: Data input error inside macro (114 lines)
      From: Long, Stuart (NIH/NIEHS) [C] <long3@NIEHS.NIH.GOV>

18. Data management question
    • Data management question (51 lines)
      From: Annie Lee <hummingbird10111@HOTMAIL.COM>
    • Re: Data management question (85 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Data management question (76 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

19. Data manipulation question
    • Data manipulation question (51 lines)
      From: Craig Hansen <c.hansen@UQ.EDU.AU>
    • Re: Data manipulation question (72 lines)
      From: Gina Nicolosi <ginanicolosi@HOTMAIL.COM>
    • Re: Data manipulation question (130 lines)
      From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
    • Re: Data manipulation question (119 lines)
      From: Craig Hansen <c.hansen@UQ.EDU.AU>
    • Re: Data manipulation question (44 lines)
      From: Gina Nicolosi <ginanicolosi@HOTMAIL.COM>
    • Re: Data manipulation question (72 lines)
      From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET>

20. Dirty Datasets from Another OS
    • Re: Dirty Datasets from Another OS (55 lines)
      From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>
    • Re: Dirty Datasets from Another OS (82 lines)
      From: Tom Hide <tom.hide@DEHIWORLD.COM>

21. Do you prefer Proc Report or Proc Tabulate?Ans,If proc report,Would you Please explain?
    • Re: Do you prefer Proc Report or Proc Tabulate?Ans,If proc report,Would you Please explain? (20 lines)
      From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>
    • Re: Do you prefer Proc Report or Proc Tabulate?Ans,If proc report,Would you Please explain? (53 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

22. ERROR 22-322: Syntax error, expecting one of the following: a name, _ALL_, _CHARACTER_,
    • ERROR 22-322: Syntax error, expecting one of the following: a name, _ALL_, _CHARACTER_, (46 lines)
      From: Irin later <irinfigvam@YAHOO.COM>
    • Re: ERROR 22-322: Syntax error, expecting one of the following: a name, _ALL_, _CHARACTER_, (26 lines)
      From: Dave Scocca <dave@SCOCCA.ORG>
    • Re: ERROR 22-322: Syntax error, expecting one of the following: a name, _ALL_, _CHARACTER_, (127 lines)
      From: Nat Wooding <Nathaniel.Wooding@DOM.COM>
    • Re: ERROR 22-322: Syntax error, expecting one of the following: a name, _ALL_, _CHARACTER_, (66 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>

23. ERROR: Subquery evaluated to more than one row
    • Re: ERROR: Subquery evaluated to more than one row (69 lines)
      From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>

24. Enterprise miner and SAS Code
    • Enterprise miner and SAS Code (22 lines)
      From: Ferran Carrascosa <ferran.carrascosa@GMAIL.COM>
    • Re: Enterprise miner and SAS Code (32 lines)
      From: Jake Bartlett <jakebartlett@GMAIL.COM>
    • Re: Enterprise miner and SAS Code (39 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

25. Expanding a dataset through the merge statement
    • Re: Expanding a dataset through the merge statement (74 lines)
      From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>

26. Extracting data out of a messy text file
    • Extracting data out of a messy text file (268 lines)
      From: Bill Behrens <mngorgeman@GMAIL.COM>
    • Re: Extracting data out of a messy text file (312 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: Extracting data out of a messy text file (110 lines)
      From: Ken Borowiak <EvilPettingZoo97@AOL.COM>
    • Re: Extracting data out of a messy text file (325 lines)
      From: Nat Wooding <Nathaniel.Wooding@DOM.COM>
    • Re: Extracting data out of a messy text file (258 lines)
      From: Bill Behrens <mngorgeman@GMAIL.COM>
    • Re: Extracting data out of a messy text file (474 lines)
      From: Nat Wooding <Nathaniel.Wooding@DOM.COM>

27. FW: SAS-callable Sudaan v9.0.1 and SAS v9.2
    • FW: SAS-callable Sudaan v9.0.1 and SAS v9.2 (46 lines)
      From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV>

28. FYI: book review of interest to MIXED fans
    • FYI: book review of interest to MIXED fans (18 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

29. GMAP/ Zip code shape file
    • GMAP/ Zip code shape file (33 lines)
      From: Treder, David <dtreder@GENESEEISD.ORG>
    • Re: GMAP/ Zip code shape file (41 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • GMAP/ Zip code shape file (95 lines)
      From: Jay Jacob Wind <jay.wind@ATT.NET>

30. HASH objects in future releases
    • HASH objects in future releases (55 lines)
      From: Denise A Kruse <krusesas@YAHOO.COM>
    • Re: HASH objects in future releases (84 lines)
      From: Paul Dorfman <sashole@BELLSOUTH.NET>
    • Re: HASH objects in future releases (120 lines)
      From: Ken Borowiak <EvilPettingZoo97@AOL.COM>

31. How does SAS find Ridge Regression RMSE?
    • How does SAS find Ridge Regression RMSE? (27 lines)
      From: Heferbob <heathandchunfang.Yates@GMAIL.COM>

32. How to Transpose Single Column
    • How to Transpose Single Column (44 lines)
      From: pprabhudesai@GMAIL.COM
    • Re: How to Transpose Single Column (108 lines)
      From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>

33. How to change Partial dates to Numeric
    • How to change Partial dates to Numeric (16 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: How to change Partial dates to Numeric (36 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: How to change Partial dates to Numeric (24 lines)
      From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV>
    • Re: How to change Partial dates to Numeric (52 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: How to change Partial dates to Numeric (70 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: How to change Partial dates to Numeric (88 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: How to change Partial dates to Numeric (115 lines)
      From: Nancy Brucken <brucken@PROVIDE.NET>

34. How to put macro do-loop code into a macro variable?
    • How to put macro do-loop code into a macro variable? (29 lines)
      From: Chris Holland <pch1969@YAHOO.COM>
    • Re: How to put macro do-loop code into a macro variable? (49 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: How to put macro do-loop code into a macro variable? (129 lines)
      From: Jack Clark <JClark@CHPDM.UMBC.EDU>
    • Re: How to put macro do-loop code into a macro variable? (66 lines)
      From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV>
    • Re: How to put macro do-loop code into a macro variable? (75 lines)
      From: Chris Holland <pch1969@YAHOO.COM>
    • Re: How to put macro do-loop code into a macro variable? (59 lines)
      From: Chris Holland <pch1969@YAHOO.COM>
    • Re: How to put macro do-loop code into a macro variable? (18 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: How to put macro do-loop code into a macro variable? (55 lines)
      From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU>
    • Re: How to put macro do-loop code into a macro variable? (42 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: How to put macro do-loop code into a macro variable? (52 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: How to put macro do-loop code into a macro variable? (132 lines)
      From: Jack Clark <JClark@CHPDM.UMBC.EDU>
    • Re: How to put macro do-loop code into a macro variable? (130 lines)
      From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV>
    • Re: How to put macro do-loop code into a macro variable? (55 lines)
      From: Ian Whitlock <iw1junk@COMCAST.NET>
    • Re: How to put macro do-loop code into a macro variable? (84 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: How to put macro do-loop code into a macro variable? (111 lines)
      From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU>
    • Re: How to put macro do-loop code into a macro variable? (38 lines)
      From: Chris Holland <pch1969@YAHOO.COM>
    • Re: How to put macro do-loop code into a macro variable? (49 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: How to put macro do-loop code into a macro variable? (45 lines)
      From: Ian Whitlock <iw1junk@COMCAST.NET>
    • Re: How to put macro do-loop code into a macro variable? (59 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: How to put macro do-loop code into a macro variable? (85 lines)
      From: Ian Whitlock <iw1junk@COMCAST.NET>
    • Re: How to put macro do-loop code into a macro variable? (100 lines)
      From: data _null_, <datanull@GMAIL.COM>

35. I Want to Stop Hard-Coding Dates
    • I Want to Stop Hard-Coding Dates (24 lines)
      From: A B <sascas@LIVE.COM>
    • Re: I Want to Stop Hard-Coding Dates (32 lines)
      From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV>
    • Re: I Want to Stop Hard-Coding Dates (58 lines)
      From: Scott Barry <sbarry@SBBWORKS.COM>
    • Re: I Want to Stop Hard-Coding Dates (74 lines)
      From: Ian Whitlock <iw1junk@COMCAST.NET>
    • Re: I Want to Stop Hard-Coding Dates (22 lines)
      From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>

36. I get to correct Dale!!!
    • I get to correct Dale!!! (30 lines)
      From: Kevin Viel <kviel@SFBRGENETICS.ORG>
    • Re: I get to correct Dale!!! (51 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>

37. Import Multiple Excel sheets using dde and macro
    • Import Multiple Excel sheets using dde and macro (44 lines)
      From: Herbert Morley A <Morley.Herbert@HCAHEALTHCARE.COM>
    • Re: Import Multiple Excel sheets using dde and macro (70 lines)
      From: Kevin Viel <kviel@SFBRGENETICS.ORG>
    • Re: Import Multiple Excel sheets using dde and macro (64 lines)
      From: Audimar P. Bangi <audi@SAS2THEMAX.COM>
    • Re: Import Multiple Excel sheets using dde and macro (64 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Import Multiple Excel sheets using dde and macro (55 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Import Multiple Excel sheets using dde and macro (70 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>

38. Importing mixed datatype fields into SAS
    • Re: Importing mixed datatype fields into SAS (103 lines)
      From: Nat Wooding <Nathaniel.Wooding@DOM.COM>

39. Infile doesn't read in all records
    • Re: Infile doesn't read in all records (91 lines)
      From: Peter <crawfordsoftware@GMAIL.COM>

40. Is SQL plenty good enough for complex data transformation?
    • Re: Is SQL plenty good enough for complex data transformation? (19 lines)
      From: Sander Burggraaff <info@BURGIE-T.NL>
    • Re: Is SQL plenty good enough for complex data transformation? (33 lines)
      From: Robert <irishhacker@GMAIL.COM>
    • Re: Is SQL plenty good enough for complex data transformation? (46 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

41. LARS (Efron et 2004) and SAS
    • LARS (Efron et 2004) and SAS (30 lines)
      From: Heferbob <heathandchunfang.Yates@GMAIL.COM>
    • Re: LARS (Efron et 2004) and SAS (44 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: LARS (Efron et 2004) and SAS (37 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

42. Libname Macro
    • Re: Libname Macro (78 lines)
      From: Peter <crawfordsoftware@GMAIL.COM>
    • Re: Libname Macro (86 lines)
      From: Machelle40 <machelle.wilchesky@MAIL.MCGILL.CA>
    • Re: Libname Macro (96 lines)
      From: data _null_; <datanull@GMAIL.COM>
    • Re: Libname Macro (102 lines)
      From: Machelle40 <machelle.wilchesky@MAIL.MCGILL.CA>

43. Loading SAS Data Set To Oracle Error
    • Re: Loading SAS Data Set To Oracle Error (81 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Loading SAS Data Set To Oracle Error (68 lines)
      From: Carol Bristow <Carol.Bristow@DPRA.COM>
    • Re: Loading SAS Data Set To Oracle Error (87 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Loading SAS Data Set To Oracle Error (107 lines)
      From: Pardee, Roy <pardee.r@GHC.ORG>

44. Log error with PROC MIANALYZE
    • Log error with PROC MIANALYZE (53 lines)
      From: Coralie <u39269@UWE.UGA.EDU>

45. Looking for Distributors/Importers: Pocket Size Welding Machine
    • Looking for Distributors/Importers: Pocket Size Welding Machine (53 lines)
      From: Manalili Machinery Enterprise <g22manalili@GMAIL.COM>
    • Re: Looking for Distributors/Importers: Pocket Size Welding Machine (56 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

46. Looping Macro Vairables
    • Re: Looping Macro Vairables (107 lines)
      From: Ian Whitlock <iw1junk@COMCAST.NET>

47. Macro question
    • Macro question (47 lines)
      From: Jerry L Diebal <jdiebal@GMAIL.COM>
    • Re: Macro question (83 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Macro question (71 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: Macro question (75 lines)
      From: Alex Tang <Alex.Tang@CREDITONE.COM>
    • Re: Macro question (78 lines)
      From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV>
    • Re: Macro question (55 lines)
      From: barry.debenham@TALK21.COM
    • Re: Macro question (111 lines)
      From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU>
    • Re: Macro question (148 lines)
      From: Alex Tang <Alex.Tang@CREDITONE.COM>
    • Re: Macro question (54 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: Macro question (71 lines)
      From: Jerry L Diebal <jdiebal@GMAIL.COM>

48. Merging datasets
    • Re: Merging datasets (22 lines)
      From: Sander Burggraaff <info@BURGIE-T.NL>

49. Missing values....
    • Re: Missing values.... (35 lines)
      From: Nirmal kumar <lazybone2k@GMAIL.COM>

50. Multiple tables next to each other Excel
    • Re: Multiple tables next to each other Excel (37 lines)
      From: MH@B&D <martin.houben@GMAIL.COM>

51. NESUG Follow-up: comments on the search facility in the new SAS tech support page
    • NESUG Follow-up: comments on the search facility in the new SAS tech support page (48 lines)
      From: Nat Wooding <Nathaniel.Wooding@DOM.COM>

52. Need Help with SAS Code! 1978 Harrison and Rubinfield Problem!
    • Need Help with SAS Code! 1978 Harrison and Rubinfield Problem! (2364 lines)
      From: mrfurley15@yahoo.com <mrfurley15@YAHOO.COM>
    • Re: Need Help with SAS Code! 1978 Harrison and Rubinfield Problem! (40 lines)
      From: Dirk Nachbar <dirknbr@GOOGLEMAIL.COM>

53. New Job : SAS Programmers USA ( East Coast ) , willing to Sponsor non US Citizens
    • New Job : SAS Programmers USA ( East Coast ) , willing to Sponsor non US Citizens (86 lines)
      From: Shula George- Please email shula@fforde-management.com <info@FFORDE-MANAGEMENT.COM>

54. New Job: Senior Contract Biostatistician USA, Will Sponsor non USA Citizens
    • New Job: Senior Contract Biostatistician USA, Will Sponsor non USA Citizens (96 lines)
      From: Shula George - Please reply to shula@fforde-management.com <info@FFORDE-MANAGEMENT.COM>

55. New Jobs in USA
    • New Jobs in USA (32 lines)
      From: Fforde Management- Please email shula@fforde-management.com <info@FFORDE-MANAGEMENT.COM>

56. New PROC REPORT conundrum
    • New PROC REPORT conundrum (54 lines)
      From: Paige Miller <paige.miller@KODAK.COM>
    • Re: New PROC REPORT conundrum (57 lines)
      From: data _null_; <datanull@GMAIL.COM>

57. ODBC -> MySQL db doesn't get WHERE clause?
    • ODBC -> MySQL db doesn't get WHERE clause? (49 lines)
      From: Pardee, Roy <pardee.r@GHC.ORG>
    • Re: ODBC -> MySQL db doesn't get WHERE clause? (69 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: ODBC -> MySQL db doesn't get WHERE clause? (91 lines)
      From: Pardee, Roy <pardee.r@GHC.ORG>
    • Re: ODBC -> MySQL db doesn't get WHERE clause? (112 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: ODBC -> MySQL db doesn't get WHERE clause? (138 lines)
      From: Pardee, Roy <pardee.r@GHC.ORG>

58. ODS the Easy Way -- A Tutorial
    • ODS the Easy Way -- A Tutorial (22 lines)
      From: Audimar P. Bangi <audi@SAS2THEMAX.COM>

59. OT: good code snippet manager
    • OT: good code snippet manager (19 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: OT: good code snippet manager (24 lines)
      From: Shanks N <shanks.n@GMAIL.COM>

60. OUTPUT WITH SURVEYMEANS/FREQ
    • Re: OUTPUT WITH SURVEYMEANS/FREQ (84 lines)
      From: Trish Bous <tbouSSARD@GMAIL.COM>

61. Optimisation - SAS OR
    • Optimisation - SAS OR (44 lines)
      From: Aj <ajeetsubramanian@GMAIL.COM>

62. PharmaSUG 2008 - Call For Papers
    • PharmaSUG 2008 - Call For Papers (39 lines)
      From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV>

63. Proc Format Error
    • Re: Proc Format Error (62 lines)
      From: RolandRB <rolandberry@HOTMAIL.COM>
    • Re: Proc Format Error (13 lines)
      From: C.A.N. <healthysheep@YAHOO.COM>
    • Re: Proc Format Error (35 lines)
      From: RolandRB <rolandberry@HOTMAIL.COM>
    • Re: Proc Format Error (60 lines)
      From: Peter <crawfordsoftware@GMAIL.COM>
    • Re: Proc Format Error (175 lines)
      From: RolandRB <rolandberry@HOTMAIL.COM>
    • Re: Proc Format Error (207 lines)
      From: Peter <crawfordsoftware@GMAIL.COM>
    • Re: Proc Format Error (31 lines)
      From: C.A.N. <healthysheep@YAHOO.COM>
    • Re: Proc Format Error (37 lines)
      From: RolandRB <rolandberry@HOTMAIL.COM>
    • Re: Proc Format Error (207 lines)
      From: RolandRB <rolandberry@HOTMAIL.COM>
    • Re: Proc Format Error (23 lines)
      From: data _null_; <datanull@GMAIL.COM>
    • Re: Proc Format Error (33 lines)
      From: RolandRB <rolandberry@HOTMAIL.COM>
    • Re: Proc Format Error (42 lines)
      From: data _null_; <datanull@GMAIL.COM>
    • Re: Proc Format Error (119 lines)
      From: Ian Whitlock <iw1junk@COMCAST.NET>
    • Re: Proc Format Error (173 lines)
      From: RolandRB <rolandberry@HOTMAIL.COM>
    • Re: Proc Format Error (159 lines)
      From: Peter <crawfordsoftware@GMAIL.COM>
    • Re: Proc Format Error (29 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: Proc Format Error (33 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Proc Format Error (51 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: Proc Format Error (124 lines)
      From: ajs2004@bigfoot.com <ajs2004@BIGFOOT.COM>
    • Re: Proc Format Error (57 lines)
      From: RolandRB <rolandberry@HOTMAIL.COM>
    • Re: Proc Format Error (65 lines)
      From: Peter <crawfordsoftware@GMAIL.COM>
    • Re: Proc Format Error (71 lines)
      From: RolandRB <rolandberry@HOTMAIL.COM>

64. Proc SQl does double EXCEPT??
    • Proc SQl does double EXCEPT?? (72 lines)
      From: Syb it <sas_datalover@YAHOO.COM>
    • Re: Proc SQl does double EXCEPT?? (96 lines)
      From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>

65. Regarding finding Oct Nov Dec Values.
    • Regarding finding Oct Nov Dec Values. (117 lines)
      From: vj <vijay_sas@HOTMAIL.COM>

66. Regarding populating values
    • Regarding populating values (236 lines)
      From: vj <vijay_sas@HOTMAIL.COM>

67. Reminder: PharmaSUG 2008 - Call For Papers
    • Reminder: PharmaSUG 2008 - Call For Papers (30 lines)
      From: Richard Read Allen <peakstat@WISPERTEL.NET>

68. Renaming the column lables
    • Renaming the column lables (68 lines)
      From: tata Birla <tata2birla@GMAIL.COM>
    • Re: Renaming the column lables (118 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Renaming the column lables (114 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Renaming the column lables (108 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>

69. SAS --> Excel
    • Re: SAS --> Excel (70 lines)
      From: Paul St Louis <pstloui@DOT.STATE.TX.US>

70. SAS 8.2 not support vista operating system
    • Re: SAS 8.2 not support vista operating system (30 lines)
      From: GAN <ganeshkumar.mohanan@GMAIL.COM>

71. SAS Error Message
    • SAS Error Message (62 lines)
      From: Bruce Allen <Bruce.B.Allen@WELLSFARGO.COM>
    • Re: SAS Error Message (86 lines)
      From: Ed Heaton <EdHeaton@WESTAT.COM>
    • Re: SAS Error Message (118 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>

72. SAS-L Digest - 17 Nov 2007 - Special issue (#2007-1901)
    • Re: SAS-L Digest - 17 Nov 2007 - Special issue (#2007-1901) (44 lines)
      From: Jay Jacob Wind <jay.wind@ATT.NET>

73. SAS-L post not going to COMP.SOFT-SYS.SAS
    • SAS-L post not going to COMP.SOFT-SYS.SAS (12 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: SAS-L post not going to COMP.SOFT-SYS.SAS (22 lines)
      From: F. J. Kelley <jkelley@UGA.EDU>

74. SAS/AF -- Frame within a Frame
    • SAS/AF -- Frame within a Frame (30 lines)
      From: Paul Walker <walker.627@OSU.EDU>
    • Re: SAS/AF -- Frame within a Frame (50 lines)
      From: Dave Scocca <dave@SCOCCA.ORG>
    • Re: SAS/AF -- Frame within a Frame (47 lines)
      From: Chris Brooks <Chris.Brooks@ONS.GOV.UK>
    • Re: SAS/AF -- Frame within a Frame (58 lines)
      From: Randy Herbison <RandyHerbison@WESTAT.COM>

75. SQL Create table vs SET DATAFILE
    • SQL Create table vs SET DATAFILE (28 lines)
      From: JumboShrimps <google@PFLAUMNET.COM>
    • Re: SQL Create table vs SET DATAFILE (32 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: SQL Create table vs SET DATAFILE (36 lines)
      From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>
    • Re: SQL Create table vs SET DATAFILE (159 lines)
      From: Ed Heaton <EdHeaton@WESTAT.COM>
    • Re: SQL Create table vs SET DATAFILE (164 lines)
      From: minze su <slhappyls@GMAIL.COM>

76. SQL Cross Join using a data step
    • Re: SQL Cross Join using a data step (34 lines)
      From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>

77. SQL or SAS or Neither?
    • SQL or SAS or Neither? (29 lines)
      From: Robert <irishhacker@GMAIL.COM>
    • Re: SQL or SAS or Neither? (56 lines)
      From: Alan Churchill <savian001@GMAIL.COM>

78. SQl Error message
    • SQl Error message (32 lines)
      From: Syb it <sas_datalover@YAHOO.COM>
    • Re: SQl Error message (37 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: SQl Error message (55 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: SQl Error message (53 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: SQl Error message (62 lines)
      From: Syb it <sas_datalover@YAHOO.COM>
    • Re: SQl Error message (56 lines)
      From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>

79. SVM in SAS : Using Soft-Margin ?
    • SVM in SAS : Using Soft-Margin ? (25 lines)
      From: Achim <google@FISKALINFORMATIKER.DE>

80. Solving integrals
    • Solving integrals (40 lines)
      From: Madan Kundu <madan4331@YAHOO.CO.IN>
    • Re: Solving integrals (58 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: Solving integrals (91 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Solving integrals (124 lines)
      From: Madan Kundu <madan4331@YAHOO.CO.IN>
    • Re: Solving integrals (37 lines)
      From: Ken Borowiak <EvilPettingZoo97@AOL.COM>

81. Starting Values
    • Starting Values (14 lines)
      From: LH <lhoopes@YAHOO.COM>
    • Re: Starting Values (14 lines)
      From: Dirk Nachbar <dirknbr@GOOGLEMAIL.COM>

82. Strong Variable Level Encryption
    • Re: Strong Variable Level Encryption (106 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Strong Variable Level Encryption (156 lines)
      From: Ed Heaton <EdHeaton@WESTAT.COM>
    • Re: Strong Variable Level Encryption (254 lines)
      From: Gerry <gpauline@PACE.EDU>
    • Re: Strong Variable Level Encryption (134 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: Strong Variable Level Encryption (67 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Strong Variable Level Encryption (100 lines)
      From: Pardee, Roy <pardee.r@GHC.ORG>

83. Transforming negative variable
    • Transforming negative variable (708 lines)
      From: William Elliott <elliott.willie@SBCGLOBAL.NET>
    • Re: Transforming negative variable (21 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Transforming negative variable (732 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: Transforming negative variable (56 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: Transforming negative variable (81 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Transforming negative variable (43 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: Transforming negative variable (561 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: Transforming negative variable (773 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: Transforming negative variable (614 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: Transforming negative variable (65 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: Transforming negative variable (543 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Transforming negative variable (626 lines)
      From: Nat Wooding <Nathaniel.Wooding@DOM.COM>
    • Re: Transforming negative variable (93 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: Transforming negative variable (57 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Transforming negative variable (22 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Transforming negative variable (127 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: Transforming negative variable (51 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: Transforming negative variable (168 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: Transforming negative variable (87 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Transforming negative variable (39 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Transforming negative variable (22 lines)
      From: William Elliott <elliott.willie@SBCGLOBAL.NET>
    • Re: Transforming negative variable (47 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: Transforming negative variable (43 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Transforming negative variable (21 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Transforming negative variable (62 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Transforming negative variable (187 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>

84. Tricky Retain Step
    • Tricky Retain Step (61 lines)
      From: George Joseph <gjman@HOTMAIL.COM>
    • Re: Tricky Retain Step (139 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: Tricky Retain Step (57 lines)
      From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET>
    • Re: Tricky Retain Step (124 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: Tricky Retain Step (29 lines)
      From: George Joseph <gjman@HOTMAIL.COM>
    • Re: Tricky Retain Step (66 lines)
      From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>
    • Re: Tricky Retain Step (60 lines)
      From: George Joseph <gjman@HOTMAIL.COM>

85. Using IML for pdf and cdf contaminated normal
    • Using IML for pdf and cdf contaminated normal (16 lines)
      From: Snow Sweeps <snowsweeps@YAHOO.COM>
    • Re: Using IML for pdf and cdf contaminated normal (56 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Using IML for pdf and cdf contaminated normal (23 lines)
      From: Snow Sweeps <snowsweeps@YAHOO.COM>
    • Re: Using IML for pdf and cdf contaminated normal (60 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Using IML for pdf and cdf contaminated normal (86 lines)
      From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU>
    • Re: Using IML for pdf and cdf contaminated normal (115 lines)
      From: Gerstle, John (CDC/CCID/NCHHSTP) (CTR) <yzg9@CDC.GOV>
    • Re: Using IML for pdf and cdf contaminated normal (132 lines)
      From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU>
    • Re: Using IML for pdf and cdf contaminated normal (133 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: Using IML for pdf and cdf contaminated normal (156 lines)
      From: Gerstle, John (CDC/CCID/NCHHSTP) (CTR) <yzg9@CDC.GOV>
    • Re: Using IML for pdf and cdf contaminated normal (67 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: Using IML for pdf and cdf contaminated normal (81 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Using IML for pdf and cdf contaminated normal (89 lines)
      From: Snow Sweeps <snowsweeps@YAHOO.COM>
    • Re: Using IML for pdf and cdf contaminated normal (59 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>

86. Visualizing Change - White Paper, Webcast, Flash Demo Available
    • Re: Visualizing Change - White Paper, Webcast, Flash Demo Available (18 lines)
      From: Sander Burggraaff <info@BURGIE-T.NL>

87. What simple tutorials do you need for Base SAS?
    • What simple tutorials do you need for Base SAS? (31 lines)
      From: RolandRB <rolandberry@HOTMAIL.COM>
    • Re: What simple tutorials do you need for Base SAS? (42 lines)
      From: RolandRB <rolandberry@HOTMAIL.COM>
    • Re: What simple tutorials do you need for Base SAS? (17 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: What simple tutorials do you need for Base SAS? (27 lines)
      From: RolandRB <rolandberry@HOTMAIL.COM>
    • Re: What simple tutorials do you need for Base SAS? (38 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>
    • Re: What simple tutorials do you need for Base SAS? (33 lines)
      From: RolandRB <rolandberry@HOTMAIL.COM>
    • Re: What simple tutorials do you need for Base SAS? (23 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: What simple tutorials do you need for Base SAS? (58 lines)
      From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US>
    • Re: What simple tutorials do you need for Base SAS? (29 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

88. Which Kind of Conjoint Analysis Can I Use?
    • Which Kind of Conjoint Analysis Can I Use? (47 lines)
      From: Chen SAS <saschen@GMAIL.COM>

89. Which type of the Conjoint Analysis is it?
    • Re: Which type of the Conjoint Analysis is it? (49 lines)
      From: Hans Zhu <saschen@GMAIL.COM>
    • Re: Which type of the Conjoint Analysis is it? (66 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>

90. Windows vs. Linux Performance
    • Windows vs. Linux Performance (22 lines)
      From: Olson, III Dean <olsonde@MSU.EDU>
    • Re: Windows vs. Linux Performance (31 lines)
      From: amada_ash@YAHOO.COM.AU
    • Re: Windows vs. Linux Performance (19 lines)
      From: Phil Rack <philrack@MINEQUEST.COM>

91. [WEB/AF ECLIPSE] Tableview Editable
    • [WEB/AF ECLIPSE] Tableview Editable (22 lines)
      From: teo22@LIBERO.IT

92. any way to sort large table faster than proc sort?
    • any way to sort large table faster than proc sort? (16 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: any way to sort large table faster than proc sort? (18 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: any way to sort large table faster than proc sort? (39 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: any way to sort large table faster than proc sort? (31 lines)
      From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
    • Re: any way to sort large table faster than proc sort? (48 lines)
      From: Wensui Liu <liuwensui@GMAIL.COM>
    • Re: any way to sort large table faster than proc sort? (67 lines)
      From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
    • Re: any way to sort large table faster than proc sort? (80 lines)
      From: T J <tj_noreply@YAHOO.COM>
    • Re: any way to sort large table faster than proc sort? (40 lines)
      From: Ed Heaton <EdHeaton@WESTAT.COM>
    • Re: any way to sort large table faster than proc sort? (27 lines)
      From: George Joseph <gjman@HOTMAIL.COM>
    • Re: any way to sort large table faster than proc sort? (17 lines)
      From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>
    • Re: any way to sort large table faster than proc sort? (24 lines)
      From: Paul Dorfman <sashole@BELLSOUTH.NET>
    • Re: any way to sort large table faster than proc sort? (53 lines)
      From: Robin Templer <templerr@CLEAR.NET.NZ>
    • Re: any way to sort large table faster than proc sort? (33 lines)
      From: Andy Arnold <awasas@COX.NET>
    • Re: any way to sort large table faster than proc sort? (27 lines)
      From: Shanks N <shanks.n@GMAIL.COM>
    • Re: any way to sort large table faster than proc sort? (75 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Re: any way to sort large table faster than proc sort? (24 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: any way to sort large table faster than proc sort? (77 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>

93. change format of a variable
    • Re: change format of a variable (69 lines)
      From: ash007 <RamsamyAshley@GMAIL.COM>
    • change format of a variable (20 lines)
      From: ash007 <RamsamyAshley@GMAIL.COM>
    • Re: change format of a variable (46 lines)
      From: anderson115@GMAIL.COM
    • Re: change format of a variable (52 lines)
      From: data _null_; <datanull@GMAIL.COM>
    • Re: change format of a variable (74 lines)
      From: data _null_, <datanull@GMAIL.COM>
    • Re: change format of a variable (44 lines)
      From: Audimar P. Bangi <audi@SAS2THEMAX.COM>
    • Re: change format of a variable (92 lines)
      From: Mary <mlhoward@AVALON.NET>

94. column to row conversion
    • Re: column to row conversion (20 lines)
      From: sassql@GMAIL.COM
    • Re: column to row conversion (39 lines)
      From: chrischown@GMAIL.COM

95. compute SEP from survival data
    • compute SEP from survival data (26 lines)
      From: duo wan <duo_wan@YAHOO.COM>

96. convert real binary to hex representation, result is out of expectation.
    • convert real binary to hex representation, result is out of expectation. (41 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>
    • Re: convert real binary to hex representation, result is out of expectation. (62 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: convert real binary to hex representation, result is out of expectation. (71 lines)
      From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV>
    • Re: convert real binary to hex representation, result is out of expectation. (116 lines)
      From: Ed Heaton <EdHeaton@WESTAT.COM>
    • Re: convert real binary to hex representation, result is out of expectation. (143 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>

97. count distinct userid using proc sql
    • Re: count distinct userid using proc sql (62 lines)
      From: Howard Schreier <hs@HOWLES.COM>

98. create matrix like table without IML
    • create matrix like table without IML (20 lines)
      From: Dirk Nachbar <dirknbr@GOOGLEMAIL.COM>
    • Re: create matrix like table without IML (99 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>

99. creating data table from many tables
    • creating data table from many tables (33 lines)
      From: andrewjmdata@GMAIL.COM
    • Re: creating data table from many tables (52 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: creating data table from many tables (65 lines)
      From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET>
    • Re: creating data table from many tables (20 lines)
      From: andrewjmdata@GMAIL.COM
    • Re: creating data table from many tables (27 lines)
      From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET>

100. data management
     • data management (45 lines)
       From: Annie Lee <hummingbird10111@HOTMAIL.COM>
     • Re: data management (78 lines)
       From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>

101. informats reading NUMERIC data
     • informats reading NUMERIC data (41 lines)
       From: RolandRB <rolandberry@HOTMAIL.COM>
     • Re: informats reading NUMERIC data (99 lines)
       From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
     • Re: informats reading NUMERIC data (155 lines)
       From: data _null_, <datanull@GMAIL.COM>
     • Re: informats reading NUMERIC data (125 lines)
       From: Ian Whitlock <iw1junk@COMCAST.NET>

102. inserting values into macro variable using array
     • inserting values into macro variable using array (34 lines)
       From: Helen <hcheng@GLOBALHEALTH.UCSF.EDU>
     • Re: inserting values into macro variable using array (61 lines)
       From: toby dunn <tobydunn@HOTMAIL.COM>
     • Re: inserting values into macro variable using array (57 lines)
       From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV>
     • Re: inserting values into macro variable using array (154 lines)
       From: Ed Heaton <EdHeaton@WESTAT.COM>
     • Re: inserting values into macro variable using array (86 lines)
       From: Paul Dorfman <sashole@BELLSOUTH.NET>

103. little library
     • Re: little library (34 lines)
       From: ash007 <RamsamyAshley@GMAIL.COM>
     • little library (19 lines)
       From: ash007 <RamsamyAshley@GMAIL.COM>
     • Re: little library (35 lines)
       From: Spjcdc <spjcdc@GMAIL.COM>
     • Re: little library (29 lines)
       From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>

104. look for better codes than mine
     • look for better codes than mine (130 lines)
       From: Jerry <greenmt@GMAIL.COM>
     • Re: look for better codes than mine (193 lines)
       From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
     • Re: look for better codes than mine (195 lines)
       From: Peetie Wheatstraw <peetie.wheatstraw@GMAIL.COM>
     • Re: look for better codes than mine (33 lines)
       From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
     • Re: look for better codes than mine (84 lines)
       From: Chang Chung <chang_y_chung@HOTMAIL.COM>
     • Re: look for better codes than mine (128 lines)
       From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>

105. optimisation
     • optimisation (26 lines)
       From: Aj <ajeetsubramanian@GMAIL.COM>
     • Re: optimisation (34 lines)
       From: Dirk Nachbar <dirknbr@GOOGLEMAIL.COM>

106. recover the number of observations of the tables of a library
     • Re: recover the number of observations of the tables of a library (71 lines)
       From: Peter <crawfordsoftware@GMAIL.COM>

107. reference code in another sas program
     • reference code in another sas program (22 lines)
       From: Captain <apsteinberg@HOTMAIL.COM>
     • Re: reference code in another sas program (33 lines)
       From: J. Manuel Picaza <JMPicaza@GMAIL.COM>
     • Re: reference code in another sas program (43 lines)
       From: Captain <apsteinberg@HOTMAIL.COM>
     • Re: reference code in another sas program (92 lines)
       From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV>
     • Re: reference code in another sas program (78 lines)
       From: Alan Churchill <savian001@GMAIL.COM>
     • Re: reference code in another sas program (96 lines)
       From: Alan Churchill <savian001@GMAIL.COM>
     • Re: reference code in another sas program (69 lines)
       From: data _null_, <datanull@GMAIL.COM>
     • Re: reference code in another sas program (89 lines)
       From: Ian Whitlock <iw1junk@COMCAST.NET>

108. regarding outputdatasets
     • Re: regarding outputdatasets (156 lines)
       From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>

109. remove the proc title from standard output listing
     • Re: remove the proc title from standard output listing (24 lines)
       From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>
     • Re: remove the proc title from standard output listing (28 lines)
       From: Ken Borowiak <EvilPettingZoo97@AOL.COM>

110. repeating a procedure on a number of variables
     • repeating a procedure on a number of variables (51 lines)
       From: Navabi, Alireza <Alireza.Navabi@AFHE.UALBERTA.CA>
     • Re: repeating a procedure on a number of variables (58 lines)
       From: Edzard van Santen <evsanten@ACESAG.AUBURN.EDU>
     • Re: repeating a procedure on a number of variables (92 lines)
       From: data _null_, <datanull@GMAIL.COM>
     • Re: repeating a procedure on a number of variables (111 lines)
       From: Navabi, Alireza <Alireza.Navabi@AFHE.UALBERTA.CA>

111. run same program on multiple files
     • run same program on multiple files (13 lines)
       From: Trish Bous <tboussard@GMAIL.COM>
     • Re: run same program on multiple files (69 lines)
       From: Dale McLerran <stringplayer_2@YAHOO.COM>
     • Re: run same program on multiple files (69 lines)
       From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV>
     • Re: run same program on multiple files (31 lines)
       From: Trish Bous <tboussard@GMAIL.COM>
     • Re: run same program on multiple files (88 lines)
       From: Dale McLerran <stringplayer_2@YAHOO.COM>
     • Re: run same program on multiple files (36 lines)
       From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>

112. run same program on multiple files-2
     • run same program on multiple files-2 (25 lines)
       From: Trish Bous <tboussard@GMAIL.COM>
     • Re: run same program on multiple files-2 (56 lines)
       From: ry2ngh@GMAIL.COM

113. sas.com community newsletters
     • sas.com community newsletters (14 lines)
       From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV>

114. second test post from SAS-L
     • second test post from SAS-L (10 lines)
       From: F. J. Kelley <jkelley@UGA.EDU>

115. second test post to comp.soft-sys.sas sent via Google Groups
     • second test post to comp.soft-sys.sas sent via Google Groups (12 lines)
       From: jkelley@uga.edu <jkelley@UGA.EDU>

116. smallest positive number?
     • smallest positive number? (12 lines)
       From: Wensui Liu <liuwensui@GMAIL.COM>
     • Re: smallest positive number? (17 lines)
       From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>
     • Re: smallest positive number? (38 lines)
       From: Wensui Liu <liuwensui@GMAIL.COM>
     • Re: smallest positive number? (20 lines)
       From: Chang Chung <chang_y_chung@HOTMAIL.COM>

117. suggestions with papers on problems of stepwise reg with existence of collinearity
     • suggestions with papers on problems of stepwise reg with existence of collinearity (22 lines)
       From: duo wan <duo_wan@YAHOO.COM>
     • Re: suggestions with papers on problems of stepwise reg with existence of collinearity (35 lines)
       From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
     • Re: suggestions with papers on problems of stepwise reg with existence of collinearity (43 lines)
       From: Snow Sweeps <snowsweeps@YAHOO.COM>
     • Re: suggestions with papers on problems of stepwise reg with existence of collinearity (44 lines)
       From: Wensui Liu <liuwensui@GMAIL.COM>

118. test post sent from SAS-L
     • test post sent from SAS-L (10 lines)
       From: F. J. Kelley <jkelley@UGA.EDU>

119. test post to comp.soft-sys.sas sent via Google groups
     • test post to comp.soft-sys.sas sent via Google groups (12 lines)
       From: jkelley@uga.edu <jkelley@UGA.EDU>

120. time data into a SAS time format
     • time data into a SAS time format (19 lines)
       From: souga soga <souga1234@GMAIL.COM>
     • Re: time data into a SAS time format (71 lines)
       From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
     • Re: time data into a SAS time format (76 lines)
       From: souga soga <souga1234@GMAIL.COM>

121. title question.
     • title question. (17 lines)
       From: Masuod Pajoh <mpajoh@ODOT.ORG>
     • Re: title question. (45 lines)
       From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>

122. transform data
     • Re: transform data (108 lines)
       From: Jerry <greenmt@GMAIL.COM>
     • Re: transform data (145 lines)
       From: data _null_, <datanull@GMAIL.COM>
     • Re: transform data (180 lines)
       From: data _null_, <datanull@GMAIL.COM>
     • Re: transform data (150 lines)
       From: Chang Chung <chang_y_chung@HOTMAIL.COM>
     • Re: transform data (169 lines)
       From: data _null_, <datanull@GMAIL.COM>
     • Re: transform data (38 lines)
       From: data _null_, <datanull@GMAIL.COM>
     • Re: transform data (83 lines)
       From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
     • Re: transform data (90 lines)
       From: data _null_, <datanull@GMAIL.COM>
     • Re: transform data (139 lines)
       From: data _null_, <datanull@GMAIL.COM>
     • Re: transform data (151 lines)
       From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>
     • Re: transform data (156 lines)
       From: data _null_, <datanull@GMAIL.COM>
     • Re: transform data (209 lines)
       From: Muthia Kachirayan <muthia.kachirayan@GMAIL.COM>

123. work space on mainframe
     • work space on mainframe (22 lines)
       From: Shiling Zhang <shiling99@YAHOO.COM>
     • Re: work space on mainframe (57 lines)
       From: Davis, Kriss P <kpdavis@ILSTU.EDU>
     • Re: work space on mainframe (87 lines)
       From: Michael Raithel <michaelraithel@WESTAT.COM>

124. x command to run acrobat distiller, but won't exit after finishing
     • x command to run acrobat distiller, but won't exit after finishing (19 lines)
       From: Ya Huang <ya.huang@AMYLIN.COM>
     • Re: x command to run acrobat distiller, but won't exit after finishing (50 lines)
       From: Ed Heaton <EdHeaton@WESTAT.COM>
     • Re: x command to run acrobat distiller, but won't exit after finishing (68 lines)
       From: Huang, Ya <Ya.Huang@AMYLIN.COM>
     • Re: x command to run acrobat distiller, but won't exit after finishing (72 lines)
       From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM>
     • Re: x command to run acrobat distiller, but won't exit after finishing (86 lines)
       From: Ya Huang <ya.huang@AMYLIN.COM>