Table of contents:

• *** AIR FRANCE CONCORD UPDATE *** (3 messages)
• Another V8 Incompatibility Issue
• Array Query (6 messages)
• BUG V8
• Books/Manuals on SAS IntrNet (2 messages)
• Brian J Kowalczyk/bkowalc/DFSI is out of the office.
• Bug in socket access method?
• CPU Time (2 messages)
• Can I verify the existence of a var. in a DATASTEP? (9 messages)
• Can the VALUE of a SAS variable be assigned to a macro variab le ?
• Can the VALUE of a SAS variable be assigned to a macro variable ? (2 messages)
• Can you View stored formats?? (5 messages)
• CfMC Mentor Database
• Combine char variables (9 messages)
• Comparison of ROC curves
• Creating NUM vars from .DBF file?
• Data from Mainframe to PC without SAS/CONNECT (2 messages)
• Dell, SAS join to monitor site visitors' actions
• Distinct in SQL: is there an id var option?
• Empty dataset - special variable (7 messages)
• Entropy R squared
• Exporting data into Excel (3 messages)
• FW: Antwort: Reading a CSV file
• FW: ODS: rtf and Xtabs
• FW: Out of Memory - SAS V8 (3 messages)
• FW: Running SAS on UNIX vs PC
• FW: how to get cumulative freq out of a proc freq
• Female to share room at NESUG
• Fuzzy Matching
• GPLOT --> Graphic stream file --> Word Perfect ??? (2 messages)
• Godfrey test?
• How do I fill an Insight variable with the present date (2 messages)
• How to identify mddb view table cell (3 messages)
• How to sign up for STAT-L? (2 messages)
• IIF function (29 messages)
• If this is the problem that my program doesn't run? (4 messages)
• Incrementing SAS date value by month (13 messages)
• Job, Phila, Clinical Programmer Analyst
• Job, Phila, Sr. Clinical Programmer Analyst
• KDD-2000 Overflow Hotel Information
• Loyalty Management System
• MVS: Re: *** AIR FRANCE CONCORD UPDATE ***
• MVS: Re: User Name and time&date when a record was updated on SAS/InterNet Application Dispatcher on SAS version 6.12.
• Merging using "fuzzy logic" (5 messages)
• MidWest SAS Users Group Conference
• Midwest SAS Users 2000 Conference Update
• Multiple t-tests and Type-I error (9 messages)
• NESUG 2000 Conference Last Day for Early Registration August 6th!!!
• NESUG 2000 early registration deadline
• NO .LST FILE - how to? (2 messages)
• Negative Sign at End of Number (4 messages)
• New SAS Web/Enablement tool
• New jobs at www.sashelp.com/jobs
• Newlines in Unix Text Data (17 messages)
• News on the SAS front - US Census
• Number the start and end position of a field in SAS View shee t
• Number the start and end position of a field in SAS View sheet (3 messages)
• ODS Drilldown and open new window (2 messages)
• ODS experts out there ??? (2 messages)
• ODS: rtf and Xtabs
• One more time-Segmentation violation (3 messages)
• PHReg in a CrossOver Study? Anyone?
• PROBLEM MACRO (4 messages)
• PROBLEM V6->V8
• PROBLEM V6->V8 (BUG V8) (2 messages)
• PROBLEM V6->V8 (SAS/ ASSIST)
• PROBLEM V6->V8 (SAS/ASSIST)
• PROC FREQ with OUT= option - using across list of variables
• PROC NLMIXED
• PROC PHREG does not recognise format statement
• Prediction of variable with 3 discreet answers (3 messages)
• Problem of copy & paste in NT/V8
• Problem of copy & paste in NT/V8 (answer from SI)
• Problems with match merge (5 messages)
• Proc Format (4 messages)
• Proc Report Question (3 messages)
• Proc Surveymeans vs PCCARP
• Q: SAS/STAT REG wrong interpretation in publication (3 messages)
• Q: perLDAP (2 messages)
• Q: provide rank value in series of variables (2 messages)
• READ QUESTION (4 messages)
• Random Assign GrouNo?? (2 messages)
• Reading a CSV file (8 messages)
• Reading zip files on a network drive
• Recap&Questions-delete subset of data set (4 messages)
• Running SAS on UNIX vs PC (3 messages)
• SAS Intrnet and Functionality of a Spreadsheet
• SAS Job - No. NJ
• SAS Job - Washington DC
• SAS POSITIONS
• SAS Position - NYC - Analyst
• SAS Positions Available/NY/PA
• SAS Programmer needed for NC
• SAS Sort Gives Erroneous Results (MVS) (4 messages)
• SAS and Unix: return codes ? (2 messages)
• SAS code for multiple comparison for KRUSKAL-WALLIS (2 messages)
• SAS job searching (2 messages)
• SAS position in Chicago area
• SAS programmer in Switzerland
• SAS v8 -> v6 (3 messages)
• SAS-Linux Experimental (2 messages)
• SAS/AF MessageBox (2 messages)
• SAS/Connect - signon (4 messages)
• SASTip: Finding tips in SAS Help (version 8)
• SCSUG 2000 Registration info
• Save the USA: Vote Green
• Save the USA: Vote for Ralph Nader (3 messages)
• Segmentation violation again.
• Segmentation violation error (4 messages)
• Selecting a Row Programmatically in a Data Table
• Should be an easy one: Informats etc.
• Standardized Coefficients with PROC LOGISTIC (2 messages)
• Subject: Re: Cobol fomat S9 (9)V99 COMP-3 convert (2 messages)
• Summary - how to assign the value of a SAS variable to a macro
• Tabbing between enhanced editor windows - NT
• Table Lookup Problem (4 messages)
• Thanks re: Log='NUL'
• The answer - Re: Howto: Programmatically clear the Results window
• Thomas H Pruitt/Contractor/Chrysler is out of the office.
• To the nice to have department (again) (2 messages)
• US-WA-Seattle SAS Programmer Needed
• Undoing Log="NUL:"
• Use Of Command Line Statements In Code (3 messages)
• User Name and time&date when a record was updated on
• User Name and time&date when a record was updated on SAS/Inte rNet Application Dispatcher on SAS version 6.12.
• User Name and time&date when a record was updated on SAS/InterNet Application Dispatcher on SAS version 6.12. (4 messages)
• V8 Printing Icon gone missin' (2 messages)
• V8 array definitions (3 messages)
• V8, What does a 'mixed-case' var name mean? (5 messages)
• V8.1 err msg: font MIA
• Was Q: SAS/STAT REG sidetopic on SAS/L value
• What's wrong with ' [ ' and X ? (3 messages)
• White t adjusted
• White t adjusted statistics (ODS OUTPUT)
• [Fwd: Q: perLDAP]
• bad data in Oracle killing query (4 messages)
• contrast codes
• counting missing values (3 messages)
• delete subset of data set (3 messages)
• find anyone anywhere in the USA 3914 (2 messages)
• fsview formula limitations
• get fileSize (diskspace) of a dataset or MDDB (4 messages)
• getting on the SAS list (3 messages)
• how many per week (2 messages)
• how to force var name truncation? (2 messages)
• how to get cumulative freq out of a proc freq (5 messages)
• info on electronic signatures (3 messages)
• iterate through all vars in a dataset (7 messages)
• medical research: type of data
• memory merge and sql cartesian product
• memory merge vs disc merge (3 messages)
• mixed date format in one column (2 messages)
• need CPT walkway (4 messages)
• not reading the last record in an INFILE/INPUT statement (2 messages)
• proc sql and cartesian product (2 messages)
• query: partial least squares discriminant analysis (2 messages)
• re - If this is the problem that my program doesn't run? (3 messages)
• reading zipped files in windows 2000 (3 messages)
• replace new value to only part of a long string variable (7 messages)
• solved: SAS/STAT REG wrong interpretation in publication
• stripping away formats (6 messages)
• subscribe and unsubscribe SAS-L
• taking *.dmp of SAS datasets (4 messages)
• upload / download files -- variable size Version 6.12, Windoze t o Unix
• variable selection in proc mixed and growth curves
• when is says "ERROR: Start is greater than end: -." (4 messages)

1. *** AIR FRANCE CONCORD UPDATE ***
   • *** AIR FRANCE CONCORD UPDATE *** (103 lines)
     From: Crash-n-Burn@TVWPO.EDU
   • Re: *** AIR FRANCE CONCORD UPDATE *** (71 lines)
     From: Philip Mason <philipmason@EMAIL.COM>
   • Re: *** AIR FRANCE CONCORD UPDATE *** (122 lines)
     From: Andre Wielki <wielki@INED.FR>

2. Another V8 Incompatibility Issue
   • Re: Another V8 Incompatibility Issue (92 lines)
     From: Larry Parker <lparker@WORLD.STD.COM>

3. Array Query
   • Array Query (60 lines)
     From: Richard.Simhon@CORNHILL.CO.UK
   • Re: Array Query (85 lines)
     From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
   • Re: Array Query (110 lines)
     From: Tift, Brian <bet5@CDC.GOV>
   • Re: Array Query (78 lines)
     From: Jay Weedon <jweedon@EARTHLINK.NET>
   • Re: Array Query (90 lines)
     From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>
   • Re: Array Query (153 lines)
     From: Ya Huang <ya.huang@AGOURON.COM>

4. BUG V8
   • BUG V8 (1046 lines)
     From: Nicolas Pont <nicolas.pont@UNICIBLE.CH>

5. Books/Manuals on SAS IntrNet
   • Books/Manuals on SAS IntrNet (21 lines)
     From: Soumen Mukherjee <SMukherjee@MAPSNET.COM>
   • Re: Books/Manuals on SAS IntrNet (68 lines)
     From: Michael Davis <michael@BASSETTCONSULTING.COM>

6. Brian J Kowalczyk/bkowalc/DFSI is out of the office.
   • Brian J Kowalczyk/bkowalc/DFSI is out of the office. (13 lines)
     From: Blackjack Player <briankowalczyk@DISCOVERFINANCIAL.COM>

7. Bug in socket access method?
   • Bug in socket access method? (69 lines)
     From: David L. Ward <dward@SASHELP.COM>

8. CPU Time
   • CPU Time (17 lines)
     From: Daniella Priscila Cruz - Estagiaria SAS <dpcruz@CENAPAD.UNICAMP.BR>
   • Re: CPU Time (40 lines)
     From: Frank Mwaniki <frank.mwaniki@PHARMA.NOVARTIS.COM>

9. Can I verify the existence of a var. in a DATASTEP?
   • Can I verify the existence of a var. in a DATASTEP? (64 lines)
     From: tom.ceyssens@ALZ.BE
   • Re: Can I verify the existence of a var. in a DATASTEP? (101 lines)
     From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
   • Re: Can I verify the existence of a var. in a DATASTEP? (115 lines)
     From: Mike Harris <mikeh@AMGEN.COM>
   • Re: Can I verify the existence of a var. in a DATASTEP? (142 lines)
     From: Vyverman, Koen <koen.vyverman@FID-INTL.COM>
   • Re: Can I verify the existence of a var. in a DATASTEP? (120 lines)
     From: Dale McLerran <dmclerra@FHCRC.ORG>
   • Re: Can I verify the existence of a var. in a DATASTEP? (29 lines)
     From: Dale McLerran <dmclerra@FHCRC.ORG>
   • Re: Can I verify the existence of a var. in a DATASTEP? (148 lines)
     From: Ian Whitlock <WHITLOI1@WESTAT.COM>
   • Re: Can I verify the existence of a var. in a DATASTEP? (238 lines)
     From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>
   • Re: Can I verify the existence of a var. in a DATASTEP? (317 lines)
     From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>

10. Can the VALUE of a SAS variable be assigned to a macro variab le ?
    • Re: Can the VALUE of a SAS variable be assigned to a macro variab le ? (84 lines)
      From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>

11. Can the VALUE of a SAS variable be assigned to a macro variable ?
    • Re: Can the VALUE of a SAS variable be assigned to a macro variable ? (49 lines)
      From: Melvin Klassen <Klassen@UVIC.CA>
    • Re: Can the VALUE of a SAS variable be assigned to a macro variable ? (60 lines)
      From: Barry Drake <Barry.Drake@OPSC.DEMON.CO.UK>

12. Can you View stored formats??
    • Can you View stored formats?? (14 lines)
      From: Tom Pruitt <thp3@DAIMLERCHRYSLER.COM>
    • Re: Can you View stored formats?? (36 lines)
      From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
    • Re: Can you View stored formats?? (61 lines)
      From: Lund, Pete <Peter.Lund@CFC.WA.GOV>
    • Re: Can you View stored formats?? (24 lines)
      From: Handsfield, James H. <jhh0@CDC.GOV>
    • Re: Can you View stored formats?? (45 lines)
      From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>

13. CfMC Mentor Database
    • CfMC Mentor Database (17 lines)
      From: Soumen Mukherjee <SMukherjee@MAPSNET.COM>

14. Combine char variables
    • Combine char variables (19 lines)
      From: Antonio <wongantonio@HONGKONG.COM>
    • Re: Combine char variables (52 lines)
      From: Greg Woolridge <greg.woolridge@TAP.COM>
    • Re: Combine char variables (80 lines)
      From: Jeremy Miller <millerj@CALIB.COM>
    • Re: Combine char variables (50 lines)
      From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV>
    • Re: Combine char variables (139 lines)
      From: Richard W. Graham <Richard.Graham@INTELLICISIONS.COM>
    • Re: Combine char variables (111 lines)
      From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM>
    • Re: Combine char variables (79 lines)
      From: Jian-an Zhu <jzhu@SPH.EMORY.EDU>
    • Re: Combine char variables (32 lines)
      From: JP <R_E_M_O_V_E_lecruguel@EPID.JGH.MCGILL.CA>
    • Re: Combine char variables (180 lines)
      From: Peter Crawford <peter.crawford@DB.COM>

15. Comparison of ROC curves
    • Comparison of ROC curves (16 lines)
      From: Simcha Pollack <pollacks@STJOHNS.EDU>

16. Creating NUM vars from .DBF file?
    • Creating NUM vars from .DBF file? (22 lines)
      From: Tom Frenkel <taf2@IS8.NYU.EDU>

17. Data from Mainframe to PC without SAS/CONNECT
    • Data from Mainframe to PC without SAS/CONNECT (38 lines)
      From: Tareq Al-Maghrabi <tareq_am@ALRAJHIBANK.COM.SA>
    • Re: Data from Mainframe to PC without SAS/CONNECT (43 lines)
      From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK>

18. Dell, SAS join to monitor site visitors' actions
    • Dell, SAS join to monitor site visitors' actions (294 lines)
      From: T. Flannery <flannery_t@HOTMAIL.COM>

19. Distinct in SQL: is there an id var option?
    • Re: Distinct in SQL: is there an id var option? (121 lines)
      From: Greg Bryant <gregbryant@EARTHLINK.NET>

20. Empty dataset - special variable
    • Empty dataset - special variable (26 lines)
      From: Shawn Ribordy <Ribordy_Shawn_C@CAT.COM>
    • Re: Empty dataset - special variable (28 lines)
      From: Fehd, Ronald J. <rjf2@CDC.GOV>
    • Re: Empty dataset - special variable (50 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
    • Re: Empty dataset - special variable (51 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Empty dataset - special variable (51 lines)
      From: charles_s_patridge@MY-DEJA.COM
    • Re: Empty dataset - special variable (111 lines)
      From: Dale McLerran <dmclerra@FHCRC.ORG>
    • Re: Empty dataset - special variable (55 lines)
      From: Dale McLerran <dmclerra@FHCRC.ORG>

21. Entropy R squared
    • Entropy R squared (13 lines)
      From: Juned Siddique <JS39@GUNET.GEORGETOWN.EDU>

22. Exporting data into Excel
    • Exporting data into Excel (44 lines)
      From: Krishnan Viswanathan <kxv9@F04S08.CAC.PSU.EDU>
    • Re: Exporting data into Excel (20 lines)
      From: Vidya <vidya.chandrasekaranNOviSPAM@WIPRO.COM.INVALID>
    • Re: Exporting data into Excel (63 lines)
      From: David Parent <sasl_2000@YAHOO.COM>

23. FW: Antwort: Reading a CSV file
    • FW: Antwort: Reading a CSV file (96 lines)
      From: Kerrison, James <James.Kerrison@FMR.COM>

24. FW: ODS: rtf and Xtabs
    • FW: ODS: rtf and Xtabs (383 lines)
      From: James Carvalho <jjc@ASU.EDU>

25. FW: Out of Memory - SAS V8
    • FW: Out of Memory - SAS V8 (26 lines)
      From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM>
    • Re: FW: Out of Memory - SAS V8 (64 lines)
      From: Tom Taylor <dtt@ACM.ORG>
    • Re: FW: Out of Memory - SAS V8 (58 lines)
      From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>

26. FW: Running SAS on UNIX vs PC
    • FW: Running SAS on UNIX vs PC (72 lines)
      From: Lesueur, Jeff, BMG Direct - NY1540 <Jeff.Lesueur@BMGDIRECT.COM>

27. FW: how to get cumulative freq out of a proc freq
    • FW: how to get cumulative freq out of a proc freq (118 lines)
      From: Claus Gotfred Rasmussen <CGR@ACCEPTCARD.DK>

28. Female to share room at NESUG
    • Female to share room at NESUG (11 lines)
      From: Karol Katz <karol.katz@YALE.EDU>

29. Fuzzy Matching
    • Fuzzy Matching (26 lines)
      From: msz03@HEALTH.STATE.NY.US

30. GPLOT --> Graphic stream file --> Word Perfect ???
    • GPLOT --> Graphic stream file --> Word Perfect ??? (134 lines)
      From: gkeeler <gkeeler@PSYCH.MC.DUKE.EDU>
    • Re: GPLOT --> Graphic stream file --> Word Perfect ??? (145 lines)
      From: Geert van Boxtel <G.J.M.vBoxtel@KUB1.NL>

31. Godfrey test?
    • Godfrey test? (24 lines)
      From: Larsson Jan <jan.larsson@SSB.NO>

32. How do I fill an Insight variable with the present date
    • How do I fill an Insight variable with the present date (16 lines)
      From: Emko Oosterhoff <e.oosterhoff@SAMSOM.NL>
    • Re: How do I fill an Insight variable with the present date (11 lines)
      From: dave_h <hapemanNOhaSPAM@JUNO.COM.INVALID>

33. How to identify mddb view table cell
    • How to identify mddb view table cell (42 lines)
      From: Devel <Devel@163.NET>
    • Re: How to identify mddb view table cell (54 lines)
      From: carlytuur@MY-DEJA.COM
    • Re: How to identify mddb view table cell (62 lines)
      From: carlytuur@MY-DEJA.COM

34. How to sign up for STAT-L?
    • How to sign up for STAT-L? (12 lines)
      From: John Jones <jonesj@PHARMARESEARCH.COM>
    • Re: How to sign up for STAT-L? (29 lines)
      From: Muhlbaier, Lawrence H. <lawrence.muhlbaier@DUKE.EDU>

35. IIF function
    • IIF function (19 lines)
      From: t_woods@MY-DEJA.COM
    • Re: IIF function (146 lines)
      From: Richard W. Graham <Richard.Graham@INTELLICISIONS.COM>
    • Re: IIF function (177 lines)
      From: Peter Crawford <peter.crawford@DB.COM>
    • Re: IIF function (38 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
    • Re: IIF function (36 lines)
      From: Nigel Pain <Nigel.Pain@SCOTLAND.GOV.UK>
    • Re: IIF function (54 lines)
      From: t_woods@MY-DEJA.COM
    • Re: IIF function (70 lines)
      From: Peter Crawford <peter.crawford@DB.COM>
    • Re: IIF function (72 lines)
      From: Amy Roehrig Swinford <aimless@FIBER.NET>
    • Re: IIF function (41 lines)
      From: Peter Crawford <peter.crawford@DB.COM>
    • Re: IIF function (23 lines)
      From: Nat Wooding <Nathaniel_Wooding@DOM.COM>
    • Re: IIF function (38 lines)
      From: Dave Steven <dcsteven@PSU.EDU>
    • Re: IIF function (27 lines)
      From: John Whittington <John.W@MEDISCIENCE.CO.UK>
    • Re: IIF function (47 lines)
      From: Cao, William <WCao@HRBLOCK.COM>
    • Re: IIF function (52 lines)
      From: Frank Mwaniki <frank.mwaniki@PHARMA.NOVARTIS.COM>
    • Re: IIF function (155 lines)
      From: Peter Crawford <peter.crawford@DB.COM>
    • Re: IIF function (28 lines)
      From: Jonathan Goldberg <Jonathan_Goldberg@MASTERCARD.COM>
    • Re: IIF function (79 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: IIF function (13 lines)
      From: Nat Wooding <Nathaniel_Wooding@DOM.COM>
    • Re: IIF function (37 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
    • Re: IIF function (60 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
    • Re: IIF function (146 lines)
      From: David Johnson <David.Johnson@UK.ROYALSUN.COM>
    • Re: IIF function (62 lines)
      From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM>
    • Re: IIF function (144 lines)
      From: Mike Harris <mikeh@AMGEN.COM>
    • Re: IIF function (43 lines)
      From: William W. Viergever <wwvierg@IBM.NET>
    • Re: IIF function (199 lines)
      From: William W. Viergever <wwvierg@IBM.NET>
    • Re: IIF function (91 lines)
      From: William W. Viergever <wwvierg@IBM.NET>
    • Re: IIF function (94 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
    • Re: IIF function (37 lines)
      From: William W. Viergever <wwvierg@IBM.NET>
    • Re: IIF function (20 lines)
      From: Peter Crawford <peter.crawford@DB.COM>

36. If this is the problem that my program doesn't run?
    • If this is the problem that my program doesn't run? (20 lines)
      From: Toni Zhang <thesis8@HOTMAIL.COM>
    • Re: If this is the problem that my program doesn't run? (44 lines)
      From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
    • Re: If this is the problem that my program doesn't run? (52 lines)
      From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>
    • Re: If this is the problem that my program doesn't run? (31 lines)
      From: Victoria M. Wilkins <victoria.wilkins@RTP.PPDI.COM>

37. Incrementing SAS date value by month
    • Incrementing SAS date value by month (20 lines)
      From: dudleyinc@MY-DEJA.COM
    • Re: Incrementing SAS date value by month (46 lines)
      From: Kerrison, James <James.Kerrison@FMR.COM>
    • Re: Incrementing SAS date value by month (26 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Incrementing SAS date value by month (73 lines)
      From: Fiona_Wade@TAC.VIC.GOV.AU
    • Re: Incrementing SAS date value by month (102 lines)
      From: CHAPMAN, John (St Leonards) <johnchapman@WESTPAC.COM.AU>
    • Re: Incrementing SAS date value by month (154 lines)
      From: Fiona_Wade@TAC.VIC.GOV.AU
    • Re: Incrementing SAS date value by month (76 lines)
      From: Bernard Tremblay <imaginasys@HOTMAIL.COM>
    • Re: Incrementing SAS date value by month (135 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Incrementing SAS date value by month (157 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
    • Re: Incrementing SAS date value by month (175 lines)
      From: Peter Crawford <peter.crawford@DB.COM>
    • Re: Incrementing SAS date value by month (37 lines)
      From: John Whittington <John.W@MEDISCIENCE.CO.UK>
    • Re: Incrementing SAS date value by month (48 lines)
      From: Ian Whitlock <WHITLOI1@WESTAT.COM>
    • Re: Incrementing SAS date value by month (204 lines)
      From: Jack Shoemaker <JShoemaker@ACCORDANT.NET>

38. Job, Phila, Clinical Programmer Analyst
    • Job, Phila, Clinical Programmer Analyst (417 lines)
      From: Ginger Redner <Gingredner@AOL.COM>

39. Job, Phila, Sr. Clinical Programmer Analyst
    • Job, Phila, Sr. Clinical Programmer Analyst (427 lines)
      From: Ginger Redner <Gingredner@AOL.COM>

40. KDD-2000 Overflow Hotel Information
    • KDD-2000 Overflow Hotel Information (57 lines)
      From: Paul Bradley <bradley@MICROSOFT.COM>

41. Loyalty Management System
    • Loyalty Management System (16 lines)
      From: Shinchan <kids_return@MYSITE.COM.HK>

42. MVS: Re: *** AIR FRANCE CONCORD UPDATE ***
    • MVS: Re: *** AIR FRANCE CONCORD UPDATE *** (43 lines)
      From: Michael A. Raithel <maraithel@EROLS.COM>

43. MVS: Re: User Name and time&date when a record was updated on SAS/InterNet Application Dispatcher on SAS version 6.12.
    • MVS: Re: User Name and time&date when a record was updated on SAS/InterNet Application Dispatcher on SAS version 6.12. (189 lines)
      From: Michael A. Raithel <maraithel@EROLS.COM>

44. Merging using "fuzzy logic"
    • Merging using "fuzzy logic" (19 lines)
      From: Frank Mwaniki <frank.mwaniki@PHARMA.NOVARTIS.COM>
    • Re: Merging using "fuzzy logic" (63 lines)
      From: charles_s_patridge@MY-DEJA.COM
    • Re: Merging using "fuzzy logic" (87 lines)
      From: charles_s_patridge@MY-DEJA.COM
    • Re: Merging using "fuzzy logic" (109 lines)
      From: Frank Mwaniki <frank.mwaniki@PHARMA.NOVARTIS.COM>
    • Re: Merging using "fuzzy logic" (69 lines)
      From: kmself@IX.NETCOM.COM

45. MidWest SAS Users Group Conference
    • MidWest SAS Users Group Conference (47 lines)
      From: Bill Adams <BillA@ADAMSCONSULT.COM>

46. Midwest SAS Users 2000 Conference Update
    • Midwest SAS Users 2000 Conference Update (55 lines)
      From: Bill Adams <BillA@ADAMSCONSULT.COM>

47. Multiple t-tests and Type-I error
    • Re: Multiple t-tests and Type-I error (76 lines)
      From: djaustin@MY-DEJA.COM
    • Re: Multiple t-tests and Type-I error (115 lines)
      From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
    • Re: Multiple t-tests and Type-I error (145 lines)
      From: Patrick McElduff <patrickm@MAIL.NEWCASTLE.EDU.AU>
    • Re: Multiple t-tests and Type-I error (210 lines)
      From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
    • Re: Multiple t-tests and Type-I error (51 lines)
      From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
    • Multiple t-tests and Type-I error (37 lines)
      From: Sorkin, John <SorkinJ@GRC.NIA.NIH.GOV>
    • Re: Multiple t-tests and Type-I error (100 lines)
      From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
    • Re: Multiple t-tests and Type-I error (97 lines)
      From: Charles.R.Jones@CCMAIL.CENSUS.GOV
    • Re: Multiple t-tests and Type-I error (22 lines)
      From: Steve Wickham <aez46@MAIL1.RRZ.UNI-KOELN.DE>

48. NESUG 2000 Conference Last Day for Early Registration August 6th!!!
    • NESUG 2000 Conference Last Day for Early Registration August 6th!!! (40 lines)
      From: Erik013@AOL.COM

49. NESUG 2000 early registration deadline
    • NESUG 2000 early registration deadline (31 lines)
      From: Sue Douglass <douglass@BA.ARS.USDA.GOV>

50. NO .LST FILE - how to?
    • NO .LST FILE - how to? (17 lines)
      From: Tom Pruitt <thp3@DAIMLERCHRYSLER.COM>
    • Re: NO .LST FILE - how to? (48 lines)
      From: Laproi, L.G.E (Louis) <Louis.Laproi@REAAL.NL>

51. Negative Sign at End of Number
    • Negative Sign at End of Number (16 lines)
      From: Kim LeBouton <Kim_LeBouton@TOYOTA.COM>
    • Re: Negative Sign at End of Number (27 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Negative Sign at End of Number (86 lines)
      From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>
    • Re: Negative Sign at End of Number (130 lines)
      From: Laproi, L.G.E (Louis) <Louis.Laproi@REAAL.NL>

52. New SAS Web/Enablement tool
    • New SAS Web/Enablement tool (30 lines)
      From: David L. Ward <dward@SASHELP.COM>

53. New jobs at www.sashelp.com/jobs
    • New jobs at www.sashelp.com/jobs (20 lines)
      From: David L. Ward <dward@SASHELP.COM>

54. Newlines in Unix Text Data
    • Newlines in Unix Text Data (21 lines)
      From: Lewis, Dan BGI SF <Dan.Lewis@BARCLAYSGLOBAL.COM>
    • Re: Newlines in Unix Text Data (45 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
    • Re: Newlines in Unix Text Data (41 lines)
      From: William W. Viergever <wwvierg@IBM.NET>
    • Re: Newlines in Unix Text Data (48 lines)
      From: David L. Ward <dward@SASHELP.COM>
    • Re: Newlines in Unix Text Data (34 lines)
      From: Richard DeVenezia <radevenz@IX.NETCOM.COM>
    • Re: Newlines in Unix Text Data (45 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
    • Re: Newlines in Unix Text Data (63 lines)
      From: kmself@IX.NETCOM.COM
    • Re: Newlines in Unix Text Data (34 lines)
      From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV>
    • Re: Newlines in Unix Text Data (62 lines)
      From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
    • Re: Newlines in Unix Text Data (81 lines)
      From: Quill, Michael <michaelq@DEMON.NET>
    • Re: Newlines in Unix Text Data (63 lines)
      From: Quill, Michael <michaelq@DEMON.NET>
    • Re: Newlines in Unix Text Data (78 lines)
      From: kmself@IX.NETCOM.COM
    • Re: Newlines in Unix Text Data (64 lines)
      From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV>
    • Re: Newlines in Unix Text Data (101 lines)
      From: Laproi, L.G.E (Louis) <Louis.Laproi@REAAL.NL>
    • Re: Newlines in Unix Text Data (133 lines)
      From: Peter Crawford <peter.crawford@DB.COM>
    • Re: Newlines in Unix Text Data (52 lines)
      From: David L. Ward <dward@SASHELP.COM>
    • Re: Newlines in Unix Text Data (155 lines)
      From: William W. Viergever <wwvierg@IBM.NET>

55. News on the SAS front - US Census
    • News on the SAS front - US Census (36 lines)
      From: Michael S Hines <mshines@PURDUE.EDU>

56. Number the start and end position of a field in SAS View shee t
    • Re: Number the start and end position of a field in SAS View shee t (84 lines)
      From: Ian Whitlock <WHITLOI1@WESTAT.COM>

57. Number the start and end position of a field in SAS View sheet
    • Number the start and end position of a field in SAS View sheet (18 lines)
      From: paula <icj808@USWEST.NET>
    • Re: Number the start and end position of a field in SAS View sheet (50 lines)
      From: Richard DeVenezia <radevenz@IX.NETCOM.COM>
    • Re: Number the start and end position of a field in SAS View sheet (65 lines)
      From: David L. Ward <dward@SASHELP.COM>

58. ODS Drilldown and open new window
    • ODS Drilldown and open new window (23 lines)
      From: bill_kossack@MY-DEJA.COM
    • Re: ODS Drilldown and open new window (60 lines)
      From: Frank Poppe <Frank.Poppe@PWCONS.COM>

59. ODS experts out there ???
    • ODS experts out there ??? (34 lines)
      From: mvs_user <trigabyte@HOTMAIL.COM>
    • Re: ODS experts out there ??? (65 lines)
      From: Frank Poppe <Frank.Poppe@PWCONS.COM>

60. ODS: rtf and Xtabs
    • ODS: rtf and Xtabs (50 lines)
      From: Jeremy Miller <millerj@CALIB.COM>

61. One more time-Segmentation violation
    • One more time-Segmentation violation (24 lines)
      From: RICH0850 <rich0850@AOL.COM>
    • Re: One more time-Segmentation violation (55 lines)
      From: kmself@IX.NETCOM.COM
    • Re: One more time-Segmentation violation (36 lines)
      From: Scott Vance <scottvance@SPRINTMAIL.COM>

62. PHReg in a CrossOver Study? Anyone?
    • PHReg in a CrossOver Study? Anyone? (12 lines)
      From: John Jones <jonesj@PHARMARESEARCH.COM>

63. PROBLEM MACRO
    • PROBLEM MACRO (61 lines)
      From: Nicolas Pont <nicolas.pont@UNICIBLE.CH>
    • PROBLEM MACRO (72 lines)
      From: Nicolas Pont <nicolas.pont@UNICIBLE.CH>
    • Re: PROBLEM MACRO (47 lines)
      From: Becker, Eckhard [IAW-04] <EBecker@VHV.DE>
    • Re: PROBLEM MACRO (126 lines)
      From: Richard DeVenezia <radevenz@IX.NETCOM.COM>

64. PROBLEM V6->V8
    • PROBLEM V6->V8 (488 lines)
      From: Nicolas Pont <nicolas.pont@UNICIBLE.CH>

65. PROBLEM V6->V8 (BUG V8)
    • PROBLEM V6->V8 (BUG V8) (1950 lines)
      From: Nicolas Pont <nicolas.pont@UNICIBLE.CH>
    • PROBLEM V6->V8 (BUG V8) (576 lines)
      From: Nicolas Pont <nicolas.pont@UNICIBLE.CH>

66. PROBLEM V6->V8 (SAS/ ASSIST)
    • PROBLEM V6->V8 (SAS/ ASSIST) (1090 lines)
      From: Nicolas Pont <nicolas.pont@UNICIBLE.CH>

67. PROBLEM V6->V8 (SAS/ASSIST)
    • PROBLEM V6->V8 (SAS/ASSIST) (398 lines)
      From: Nicolas Pont <nicolas.pont@UNICIBLE.CH>

68. PROC FREQ with OUT= option - using across list of variables
    • PROC FREQ with OUT= option - using across list of variables (69 lines)
      From: Barry Walton <bwalton@MARAUDER.MILLERSV.EDU>

69. PROC NLMIXED
    • PROC NLMIXED (19 lines)
      From: Bart Spiessens <Bart.Spiessens@MED.KULEUVEN.AC.BE>

70. PROC PHREG does not recognise format statement
    • PROC PHREG does not recognise format statement (122 lines)
      From: Paul Dickman <paul.dickman@MEP.KI.SE>

71. Prediction of variable with 3 discreet answers
    • Prediction of variable with 3 discreet answers (21 lines)
      From: David Parent <dparent@UCLA.EDU>
    • Re: Prediction of variable with 3 discreet answers (35 lines)
      From: Soumen Mukherjee <SMukherjee@MAPSNET.COM>
    • Re: Prediction of variable with 3 discreet answers (58 lines)
      From: Dave Cameron <DCameron@MERKLENET.COM>

72. Problem of copy & paste in NT/V8
    • Problem of copy & paste in NT/V8 (30 lines)
      From: Ya Huang <ya.huang@AGOURON.COM>

73. Problem of copy & paste in NT/V8 (answer from SI)
    • Re: Problem of copy & paste in NT/V8 (answer from SI) (37 lines)
      From: Ya Huang <ya.huang@AGOURON.COM>

74. Problems with match merge
    • Problems with match merge (40 lines)
      From: ibabeu@MY-DEJA.COM
    • Re: Problems with match merge (68 lines)
      From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>
    • Re: Problems with match merge (65 lines)
      From: hipp3@MY-DEJA.COM
    • Re: Problems with match merge (63 lines)
      From: charles_s_patridge@MY-DEJA.COM
    • Re: Problems with match merge (156 lines)
      From: Amy Roehrig Swinford <aimless@FIBER.NET>

75. Proc Format
    • Proc Format (13 lines)
      From: Jon <jont@YEBO.CO.ZA>
    • Re: Proc Format (34 lines)
      From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
    • Re: Proc Format (23 lines)
      From: Fehd, Ronald J. <rjf2@CDC.GOV>
    • Re: Proc Format (49 lines)
      From: Jon <jont@YEBO.CO.ZA>

76. Proc Report Question
    • Re: Proc Report Question (16 lines)
      From: dave_h <hapeman@JUNO.COM>
    • Re: Proc Report Question (28 lines)
      From: William W. Viergever <wwvierg@IBM.NET>
    • Re: Proc Report Question (11 lines)
      From: dave_h <hapemanNOhaSPAM@JUNO.COM.INVALID>

77. Proc Surveymeans vs PCCARP
    • Proc Surveymeans vs PCCARP (51 lines)
      From: bob7469@MY-DEJA.COM

78. Q: SAS/STAT REG wrong interpretation in publication
    • Q: SAS/STAT REG wrong interpretation in publication (35 lines)
      From: Christian F.G. Schendera <schendera@NIKOCITY.DE>
    • Re: Q: SAS/STAT REG wrong interpretation in publication (83 lines)
      From: Dale McLerran <dmclerra@FHCRC.ORG>
    • Re: Q: SAS/STAT REG wrong interpretation in publication (13 lines)
      From: Kerrison, James <James.Kerrison@FMR.COM>

79. Q: perLDAP
    • Q: perLDAP (45 lines)
      From: Michael Thomas <mjthom4@USWEST.COM>
    • Re: Q: perLDAP (46 lines)
      From: Gerry Pauline <GPauline@FSMAIL.PACE.EDU>

80. Q: provide rank value in series of variables
    • Q: provide rank value in series of variables (58 lines)
      From: Fehd, Ronald J. <rjf2@CDC.GOV>
    • Re: Q: provide rank value in series of variables (100 lines)
      From: Hay, Mary Sue <OIG> <Mary.Sue.Hay@OIG.DOT.GOV>

81. READ QUESTION
    • READ QUESTION (41 lines)
      From: Nicolas Pont <nicolas.pont@UNICIBLE.CH>
    • Re: READ QUESTION (158 lines)
      From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV>
    • Re: READ QUESTION (111 lines)
      From: Ian Whitlock <WHITLOI1@WESTAT.COM>
    • Re: READ QUESTION (64 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>

82. Random Assign GrouNo??
    • Random Assign GrouNo?? (17 lines)
      From: Jing Liu <mengq99@HOTMAIL.COM>
    • Re: Random Assign GrouNo?? (37 lines)
      From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>

83. Reading a CSV file
    • Reading a CSV file (29 lines)
      From: Kerrison, James <James.Kerrison@FMR.COM>
    • Re: Reading a CSV file (55 lines)
      From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
    • Re: Reading a CSV file (33 lines)
      From: Melvin Klassen <Klassen@UVIC.CA>
    • Re: Reading a CSV file (57 lines)
      From: Kerrison, James <James.Kerrison@FMR.COM>
    • Re: Reading a CSV file (26 lines)
      From: William W. Viergever <wwvierg@IBM.NET>
    • Re: Reading a CSV file (42 lines)
      From: Kerrison, James <James.Kerrison@FMR.COM>
    • Re: Reading a CSV file (83 lines)
      From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
    • Re: Reading a CSV file (98 lines)
      From: Kerrison, James <James.Kerrison@FMR.COM>

84. Reading zip files on a network drive
    • Re: Reading zip files on a network drive (92 lines)
      From: z <gzuckierNOgzSPAM@MY-DEJANEWS.COM.INVALID>

85. Recap&Questions-delete subset of data set
    • Recap&Questions-delete subset of data set (46 lines)
      From: Jonatan Nunez <Jonatan.Nunez@MSDW.COM>
    • Re: Recap&Questions-delete subset of data set (80 lines)
      From: Abelson_R <Abelson_R@BLS.GOV>
    • Re: Recap&Questions-delete subset of data set (34 lines)
      From: dkb@CIX.COMPULINK.CO.UK
    • Re: Recap&Questions-delete subset of data set (68 lines)
      From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM>

86. Running SAS on UNIX vs PC
    • Running SAS on UNIX vs PC (16 lines)
      From: Kanagasabai Nadarajah <knada@ACESAG.AUBURN.EDU>
    • Re: Running SAS on UNIX vs PC (29 lines)
      From: Jian-an Zhu <jzhu@SPH.EMORY.EDU>
    • Re: Running SAS on UNIX vs PC (42 lines)
      From: Muhlbaier, Lawrence H. <lawrence.muhlbaier@DUKE.EDU>

87. SAS Intrnet and Functionality of a Spreadsheet
    • SAS Intrnet and Functionality of a Spreadsheet (11 lines)
      From: Wesley Shaw <Wesley_Shaw@DOM.COM>

88. SAS Job - No. NJ
    • SAS Job - No. NJ (27 lines)
      From: Jeff Neubert <geyser34@YAHOO.COM>

89. SAS Job - Washington DC
    • SAS Job - Washington DC (18 lines)
      From: ik7565@EROLS.COM

90. SAS POSITIONS
    • SAS POSITIONS (20 lines)
      From: Lemaire Aline <alemaire@CONSULTEM.COM>

91. SAS Position - NYC - Analyst
    • SAS Position - NYC - Analyst (26 lines)
      From: Howard <howard@AD-CO.COM>

92. SAS Positions Available/NY/PA
    • SAS Positions Available/NY/PA (90 lines)
      From: SMChris <knowltongroup@YAHOO.COM>

93. SAS Programmer needed for NC
    • SAS Programmer needed for NC (48 lines)
      From: Mike Sigman-Tech Associates <tech@CHARM.NET>

94. SAS Sort Gives Erroneous Results (MVS)
    • Re: SAS Sort Gives Erroneous Results (MVS) (96 lines)
      From: Lawson, Gavin <gavin.lawson@QR.COM.AU>
    • Re: SAS Sort Gives Erroneous Results (MVS) (129 lines)
      From: Frank Mwaniki <frank.mwaniki@PHARMA.NOVARTIS.COM>
    • Re: SAS Sort Gives Erroneous Results (MVS) (151 lines)
      From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>
    • Re: SAS Sort Gives Erroneous Results (MVS) (230 lines)
      From: Frank Mwaniki <frank.mwaniki@PHARMA.NOVARTIS.COM>

95. SAS and Unix: return codes ?
    • SAS and Unix: return codes ? (31 lines)
      From: Evert Carton <ecarton@CRL.BE>
    • Re: SAS and Unix: return codes ? (77 lines)
      From: Evert Carton <ecarton@CRL.BE>

96. SAS code for multiple comparison for KRUSKAL-WALLIS
    • Re: SAS code for multiple comparison for KRUSKAL-WALLIS (20 lines)
      From: Mr J Simakani <SIMAKANI.acd.UTT.UTR@GETAFIX.UTR.AC.ZA>
    • Re: SAS code for multiple comparison for KRUSKAL-WALLIS (35 lines)
      From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV>

97. SAS job searching
    • SAS job searching (17 lines)
      From: JYong <jyong00@FUDAN.EDU>
    • Re: SAS job searching (47 lines)
      From: charles_s_patridge@MY-DEJA.COM

98. SAS position in Chicago area
    • SAS position in Chicago area (30 lines)
      From: zhuanxuiowa@MY-DEJA.COM

99. SAS programmer in Switzerland
    • SAS programmer in Switzerland (12 lines)
      From: Fabrizio <fabrizio.de-amicis@JRC.IT>

100. SAS v8 -> v6
     • SAS v8 -> v6 (31 lines)
       From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM>
     • Re: SAS v8 -> v6 (76 lines)
       From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>
     • Re: SAS v8 -> v6 (44 lines)
       From: Melvin Klassen <Klassen@UVIC.CA>

101. SAS-Linux Experimental
     • SAS-Linux Experimental (48 lines)
       From: David L. Ward <dward@SASHELP.COM>
     • Re: SAS-Linux Experimental (33 lines)
       From: Daniel Normolle <monk@UMICH.EDU>

102. SAS/AF MessageBox
     • SAS/AF MessageBox (16 lines)
       From: Michael Bisfelt <mhb78@POST6.TELE.DK>
     • Re: SAS/AF MessageBox (89 lines)
       From: Richard DeVenezia <radevenz@IX.NETCOM.COM>

103. SAS/Connect - signon
     • SAS/Connect - signon (27 lines)
       From: ldion@MY-DEJA.COM
     • Re: SAS/Connect - signon (48 lines)
       From: Ray Pass <raypass@WORLDNET.ATT.NET>
     • Re: SAS/Connect - signon (136 lines)
       From: David Johnson <David.Johnson@UK.ROYALSUN.COM>
     • Re: SAS/Connect - signon (90 lines)
       From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL>

104. SASTip: Finding tips in SAS Help (version 8)
     • SASTip: Finding tips in SAS Help (version 8) (26 lines)
       From: Philip Mason <philipmason@EMAIL.COM>

105. SCSUG 2000 Registration info
     • SCSUG 2000 Registration info (68 lines)
       From: Clarence Wm. Jackson, CQA <CJac@COMPUSERVE.COM>

106. Save the USA: Vote Green
     • Save the USA: Vote Green (123 lines)
       From: Connie Mack <connie@MACK.SENATE.GOV>

107. Save the USA: Vote for Ralph Nader
     • Save the USA: Vote for Ralph Nader (153 lines)
       From: Tim Hutchinson <senator.hutchinson@HUTCHINSON.SENATE.GOV>
     • Re: Save the USA: Vote for Ralph Nader (42 lines)
       From: Paul M. Dorfman <sashole@MEDIAONE.NET>
     • Re: Save the USA: Vote for Ralph Nader (36 lines)
       From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>

108. Segmentation violation again.
     • Segmentation violation again. (8 lines)
       From: RICH0850 <rich0850@AOL.COM>

109. Segmentation violation error
     • Segmentation violation error (20 lines)
       From: RICH0850 <rich0850@AOL.COM>
     • Re: Segmentation violation error (53 lines)
       From: Ian Whitlock <WHITLOI1@WESTAT.COM>
     • Re: Segmentation violation error (185 lines)
       From: William W. Viergever <wwvierg@IBM.NET>
     • Re: Segmentation violation error (39 lines)
       From: Dwight Eggers (EUS) <EUSDEE1@AM1.ERICSSON.SE>

110. Selecting a Row Programmatically in a Data Table
     • Selecting a Row Programmatically in a Data Table (12 lines)
       From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM>

111. Should be an easy one: Informats etc.
     • Should be an easy one: Informats etc. (55 lines)
       From: Mark Moran <Mark.K.Moran@CCMAIL.CENSUS.GOV>

112. Standardized Coefficients with PROC LOGISTIC
     • Standardized Coefficients with PROC LOGISTIC (17 lines)
       From: hiemstra@YAHOO.COM
     • Re: Standardized Coefficients with PROC LOGISTIC (30 lines)
       From: Stuart Drucker <sdrucker@PIPELINE.COM>

113. Subject: Re: Cobol fomat S9 (9)V99 COMP-3 convert
     • Re: Subject: Re: Cobol fomat S9 (9)V99 COMP-3 convert (102 lines)
       From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>
     • Re: Subject: Re: Cobol fomat S9 (9)V99 COMP-3 convert (80 lines)
       From: Lambert, Bob <Bob_Lambert@AFCC.COM>

114. Summary - how to assign the value of a SAS variable to a macro
     • Summary - how to assign the value of a SAS variable to a macro (30 lines)
       From: Barry Walton <bwalton@MARAUDER.MILLERSV.EDU>

115. Tabbing between enhanced editor windows - NT
     • Re: Tabbing between enhanced editor windows - NT (37 lines)
       From: Frank Poppe <Frank.Poppe@PWCONS.COM>

116. Table Lookup Problem
     • Table Lookup Problem (25 lines)
       From: Wei-heng Lin <whlin@HPV2K.CC.CYCU.EDU.TW>
     • Re: Table Lookup Problem (147 lines)
       From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>
     • Re: Table Lookup Problem (178 lines)
       From: Wei-heng Lin <wlin@TAIWAN.COM>
     • Re: Table Lookup Problem (81 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>

117. Thanks re: Log='NUL'
     • Thanks re: Log='NUL' (11 lines)
       From: Yvonne R. Thompson <yvonnet@ANDREW.CMU.EDU>

118. The answer - Re: Howto: Programmatically clear the Results window
     • Re: The answer - Re: Howto: Programmatically clear the Results window (115 lines)
       From: Mark Van De Vyver <mvdv@BIGFOOT.COM>

119. Thomas H Pruitt/Contractor/Chrysler is out of the office.
     • Thomas H Pruitt/Contractor/Chrysler is out of the office. (11 lines)
       From: Tom Pruitt <thp3@DAIMLERCHRYSLER.COM>

120. To the nice to have department (again)
     • To the nice to have department (again) (15 lines)
       From: Jon <jont@YEBO.CO.ZA>
     • Re: To the nice to have department (again) (40 lines)
       From: Claus Gotfred Rasmussen <CGR@ACCEPTCARD.DK>

121. US-WA-Seattle SAS Programmer Needed
     • US-WA-Seattle SAS Programmer Needed (40 lines)
       From: roger@EDCNET.COM

122. Undoing Log="NUL:"
     • Re: Undoing Log="NUL:" (50 lines)
       From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>

123. Use Of Command Line Statements In Code
     • Use Of Command Line Statements In Code (13 lines)
       From: David Fleet <davidfleet@DATAMAGIK.CO.UK>
     • Re: Use Of Command Line Statements In Code (123 lines)
       From: Richard W. Graham <Richard.Graham@INTELLICISIONS.COM>
     • Re: Use Of Command Line Statements In Code (52 lines)
       From: Fehd, Ronald J. <rjf2@CDC.GOV>

124. User Name and time&date when a record was updated on
     • Re: User Name and time&date when a record was updated on (36 lines)
       From: Michael Davis <sas-l@BASSETTCONSULTING.COM>

125. User Name and time&date when a record was updated on SAS/Inte rNet Application Dispatcher on SAS version 6.12.
     • Re: User Name and time&date when a record was updated on SAS/Inte rNet Application Dispatcher on SAS version 6.12. (92 lines)
       From: Shiferaw_G <Shiferaw_G@BLS.GOV>

126. User Name and time&date when a record was updated on SAS/InterNet Application Dispatcher on SAS version 6.12.
     • User Name and time&date when a record was updated on SAS/InterNet Application Dispatcher on SAS version 6.12. (24 lines)
       From: Shiferaw_G <Shiferaw_G@BLS.GOV>
     • Re: User Name and time&date when a record was updated on SAS/InterNet Application Dispatcher on SAS version 6.12. (57 lines)
       From: Michael Davis <sas-l@BASSETTCONSULTING.COM>
     • Re: User Name and time&date when a record was updated on SAS/InterNet Application Dispatcher on SAS version 6.12. (110 lines)
       From: Michael A. Raithel <maraithel@EROLS.COM>
     • Re: User Name and time&date when a record was updated on SAS/InterNet Application Dispatcher on SAS version 6.12. (46 lines)
       From: Richard DeVenezia <radevenz@IX.NETCOM.COM>

127. V8 Printing Icon gone missin'
     • V8 Printing Icon gone missin' (30 lines)
       From: John Gerstle <JGerstle@SW.UA.EDU>
     • Re: V8 Printing Icon gone missin' (50 lines)
       From: Mike Rhoads <RHOADSM1@WESTAT.COM>

128. V8 array definitions
     • V8 array definitions (54 lines)
       From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM>
     • Re: V8 array definitions (53 lines)
       From: Fehd, Ronald J. <rjf2@CDC.GOV>
     • Re: V8 array definitions (66 lines)
       From: Lex Jansen <l.jansen@LEX-JANSEN.DEMON.NL>

129. V8, What does a 'mixed-case' var name mean?
     • V8, What does a 'mixed-case' var name mean? (23 lines)
       From: Ya Huang <ya.huang@AGOURON.COM>
     • Re: V8, What does a 'mixed-case' var name mean? (35 lines)
       From: Meldrum, Sean <Sean_Meldrum@URMC.ROCHESTER.EDU>
     • Re: V8, What does a 'mixed-case' var name mean? (22 lines)
       From: Fehd, Ronald J. <rjf2@CDC.GOV>
     • Re: V8, What does a 'mixed-case' var name mean? (58 lines)
       From: Fehd, Ronald J. <rjf2@CDC.GOV>
     • Re: V8, What does a 'mixed-case' var name mean? (46 lines)
       From: Nick Paszty <npaszty@ORGANIC.COM>

130. V8.1 err msg: font MIA
     • Re: V8.1 err msg: font MIA (73 lines)
       From: haworthl@MINDSPRING.COM

131. Was Q: SAS/STAT REG sidetopic on SAS/L value
     • Was Q: SAS/STAT REG sidetopic on SAS/L value (97 lines)
       From: David Johnson <David.Johnson@UK.ROYALSUN.COM>

132. What's wrong with ' [ ' and X ?
     • What's wrong with ' [ ' and X ? (89 lines)
       From: David Wright <david_20000@HOTMAIL.COM>
     • Re: What's wrong with ' [ ' and X ? (76 lines)
       From: Paige Miller <paige.miller@KODAK.COM>
     • Re: What's wrong with ' [ ' and X ? (114 lines)
       From: David Wright <david_20000@HOTMAIL.COM>

133. White t adjusted
     • White t adjusted (68 lines)
       From: Christian Petersen <cp.acc@CBS.DK>

134. White t adjusted statistics (ODS OUTPUT)
     • White t adjusted statistics (ODS OUTPUT) (34 lines)
       From: Christian Petersen <cp.acc@CBS.DK>

135. [Fwd: Q: perLDAP]
     • [Fwd: Q: perLDAP] (55 lines)
       From: Michael Thomas <mjthom4@USWEST.COM>

136. bad data in Oracle killing query
     • bad data in Oracle killing query (19 lines)
       From: bill_kossack@MY-DEJA.COM
     • Re: bad data in Oracle killing query (28 lines)
       From: Jon <jont@YEBO.CO.ZA>
     • Re: bad data in Oracle killing query (46 lines)
       From: bill_kossack@MY-DEJA.COM
     • Re: bad data in Oracle killing query (39 lines)
       From: Gary Moran <mvs.sig@OOPSBTINTERNET.COM>

137. contrast codes
     • contrast codes (26 lines)
       From: Andrew McCulloch <amccul@ESSEX.AC.UK>

138. counting missing values
     • counting missing values (14 lines)
       From: bill_kossack@MY-DEJA.COM
     • Re: counting missing values (27 lines)
       From: Ya Huang <ya.huang@AGOURON.COM>
     • Re: counting missing values (44 lines)
       From: Jules Bosch <jules@BOSCHSYSTEMS.COM>

139. delete subset of data set
     • delete subset of data set (23 lines)
       From: Jonatan Nunez <Jonatan.Nunez@MSDW.COM>
     • Re: delete subset of data set (150 lines)
       From: Richard W. Graham <Richard.Graham@INTELLICISIONS.COM>
     • Re: delete subset of data set (36 lines)
       From: Laurie Fleming <lflemingNOlfSPAM@ACTRIX.GEN.NZ.INVALID>

140. find anyone anywhere in the USA 3914
     • find anyone anywhere in the USA 3914 (11 lines)
       From: ncpgqb@PEOPLESEARCH-4U.COM
     • Re: find anyone anywhere in the USA 3914 (21 lines)
       From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV>

141. fsview formula limitations
     • fsview formula limitations (20 lines)
       From: Peter Crawford <peter.crawford@DB.COM>

142. get fileSize (diskspace) of a dataset or MDDB
     • get fileSize (diskspace) of a dataset or MDDB (17 lines)
       From: murer@MY-DEJA.COM
     • Re: get fileSize (diskspace) of a dataset or MDDB (43 lines)
       From: Laproi, L.G.E (Louis) <Louis.Laproi@REAAL.NL>
     • Re: get fileSize (diskspace) of a dataset or MDDB (38 lines)
       From: autretx@MY-DEJA.COM
     • Re: get fileSize (diskspace) of a dataset or MDDB (131 lines)
       From: Richard W. Graham <Richard.Graham@INTELLICISIONS.COM>

143. getting on the SAS list
     • getting on the SAS list (20 lines)
       From: Reshama Shaikh <reshama@EMAIL.COM>
     • Re: getting on the SAS list (41 lines)
       From: F.J. Kelley <jkelley@ARCHES.UGA.EDU>
     • Re: getting on the SAS list (31 lines)
       From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM>

144. how many per week
     • how many per week (20 lines)
       From: bill_kossack@MY-DEJA.COM
     • Re: how many per week (72 lines)
       From: David L. Ward <dward@SASHELP.COM>

145. how to force var name truncation?
     • how to force var name truncation? (69 lines)
       From: Terjeson, Mark <TERJEMW@DSHS.WA.GOV>
     • Re: how to force var name truncation? (87 lines)
       From: Jack Shoemaker <JShoemaker@ACCORDANT.NET>

146. how to get cumulative freq out of a proc freq
     • how to get cumulative freq out of a proc freq (16 lines)
       From: Claus Gotfred Rasmussen <CGR@ACCEPTCARD.DK>
     • Re: how to get cumulative freq out of a proc freq (29 lines)
       From: Fehd, Ronald J. <rjf2@CDC.GOV>
     • Re: how to get cumulative freq out of a proc freq (83 lines)
       From: Claus Gotfred Rasmussen <CGR@ACCEPTCARD.DK>
     • Re: how to get cumulative freq out of a proc freq (35 lines)
       From: Paige Miller <paige.miller@KODAK.COM>
     • Re: how to get cumulative freq out of a proc freq (88 lines)
       From: Dale McLerran <dmclerra@FHCRC.ORG>

147. info on electronic signatures
     • info on electronic signatures (23 lines)
       From: melissa <melissa@PHOR.COM>
     • Re: info on electronic signatures (36 lines)
       From: Gerry Pauline <GPauline@FSMAIL.PACE.EDU>
     • Re: info on electronic signatures (39 lines)
       From: Muhlbaier, Lawrence H. <lawrence.muhlbaier@DUKE.EDU>

148. iterate through all vars in a dataset
     • iterate through all vars in a dataset (71 lines)
       From: Sterling Price <ssprice@WAL-MART.COM>
     • Re: iterate through all vars in a dataset (111 lines)
       From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
     • Re: iterate through all vars in a dataset (111 lines)
       From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>
     • Re: iterate through all vars in a dataset (162 lines)
       From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
     • Re: iterate through all vars in a dataset (93 lines)
       From: Peter Crawford <peter.crawford@DB.COM>
     • Re: iterate through all vars in a dataset (136 lines)
       From: Sterling Price <ssprice@WAL-MART.COM>
     • Re: iterate through all vars in a dataset (175 lines)
       From: Peter Crawford <peter.crawford@DB.COM>

149. medical research: type of data
     • medical research: type of data (45 lines)
       From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK>

150. memory merge and sql cartesian product
     • Re: memory merge and sql cartesian product (15 lines)
       From: Lesueur, Jeff, BMG Direct - NY1540 <Jeff.Lesueur@BMGDIRECT.COM>

151. memory merge vs disc merge
     • memory merge vs disc merge (24 lines)
       From: Lesueur, Jeff, BMG Direct - NY1540 <Jeff.Lesueur@BMGDIRECT.COM>
     • Re: memory merge vs disc merge (68 lines)
       From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>
     • Re: memory merge vs disc merge (72 lines)
       From: kmself@IX.NETCOM.COM

152. mixed date format in one column
     • Re: mixed date format in one column (224 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: mixed date format in one column (250 lines)
       From: paula <icj808@USWEST.NET>

153. need CPT walkway
     • Re: need CPT walkway (35 lines)
       From: Muhlbaier, Lawrence H. <lawrence.muhlbaier@DUKE.EDU>
     • Re: need CPT walkway (33 lines)
       From: William W. Viergever <wwvierg@IBM.NET>
     • Re: need CPT walkway (55 lines)
       From: Jack Shoemaker <JShoemaker@ACCORDANT.NET>
     • Re: need CPT walkway (69 lines)
       From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>

154. not reading the last record in an INFILE/INPUT statement
     • Re: not reading the last record in an INFILE/INPUT statement (151 lines)
       From: Nigel Pain <Nigel.Pain@SCOTLAND.GOV.UK>
     • Re: not reading the last record in an INFILE/INPUT statement (186 lines)
       From: Claus Gotfred Rasmussen <CGR@ACCEPTCARD.DK>

155. proc sql and cartesian product
     • proc sql and cartesian product (11 lines)
       From: Lesueur, Jeff, BMG Direct - NY1540 <Jeff.Lesueur@BMGDIRECT.COM>
     • Re: proc sql and cartesian product (64 lines)
       From: David Johnson <David.Johnson@UK.ROYALSUN.COM>

156. query: partial least squares discriminant analysis
     • Re: query: partial least squares discriminant analysis (29 lines)
       From: Paige Miller <paige.miller@KODAK.COM>
     • Re: query: partial least squares discriminant analysis (38 lines)
       From: Paige Miller <paige.miller@KODAK.COM>

157. re - If this is the problem that my program doesn't run?
     • re - If this is the problem that my program doesn't run? (61 lines)
       From: Catherine Van Aerden <VANAERC@WESTAT.COM>
     • Re: re - If this is the problem that my program doesn't run? (15 lines)
       From: Meldrum, Sean <Sean_Meldrum@URMC.ROCHESTER.EDU>
     • Re: re - If this is the problem that my program doesn't run? (39 lines)
       From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>

158. reading zipped files in windows 2000
     • Re: reading zipped files in windows 2000 (87 lines)
       From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
     • Re: reading zipped files in windows 2000 (36 lines)
       From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV>
     • Re: reading zipped files in windows 2000 (33 lines)
       From: Jay Weedon <jweedon@EARTHLINK.NET>

159. replace new value to only part of a long string variable
     • replace new value to only part of a long string variable (21 lines)
       From: Toni Zhang <thesis8@HOTMAIL.COM>
     • Re: replace new value to only part of a long string variable (34 lines)
       From: John Whittington <John.W@MEDISCIENCE.CO.UK>
     • Re: replace new value to only part of a long string variable (68 lines)
       From: Greg Woolridge <greg.woolridge@TAP.COM>
     • Re: replace new value to only part of a long string variable (89 lines)
       From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM>
     • Re: replace new value to only part of a long string variable (114 lines)
       From: Nigel Pain <Nigel.Pain@SCOTLAND.GOV.UK>
     • Re: replace new value to only part of a long string variable (142 lines)
       From: Greg Woolridge <greg.woolridge@TAP.COM>
     • Re: replace new value to only part of a long string variable (46 lines)
       From: John Whittington <John.W@MEDISCIENCE.CO.UK>

160. solved: SAS/STAT REG wrong interpretation in publication
     • solved: SAS/STAT REG wrong interpretation in publication (13 lines)
       From: Christian F.G. Schendera <schendera@NIKOCITY.DE>

161. stripping away formats
     • stripping away formats (56 lines)
       From: T. Flannery <flannery_t@HOTMAIL.COM>
     • Re: stripping away formats (177 lines)
       From: Richard W. Graham <Richard.Graham@INTELLICISIONS.COM>
     • Re: stripping away formats (69 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: stripping away formats (144 lines)
       From: Peter Crawford <peter.crawford@DB.COM>
     • Re: stripping away formats (89 lines)
       From: Ian Whitlock <WHITLOI1@WESTAT.COM>
     • Re: stripping away formats (32 lines)
       From: Nat Wooding <Nathaniel_Wooding@DOM.COM>

162. subscribe and unsubscribe SAS-L
     • subscribe and unsubscribe SAS-L (17 lines)
       From: Wu Consulting <wuconsultinginc@HOTMAIL.COM>

163. taking *.dmp of SAS datasets
     • taking *.dmp of SAS datasets (25 lines)
       From: Vidya <vidya.chandrasekaranNOviSPAM@WIPRO.COM.INVALID>
     • Re: taking *.dmp of SAS datasets (46 lines)
       From: Peter Crawford <peter.crawford@DB.COM>
     • Re: taking *.dmp of SAS datasets (68 lines)
       From: Deepak Mathur <Deepak.Mathur@ORANGE.CO.IN>
     • Re: taking *.dmp of SAS datasets (34 lines)
       From: Vidya <vidya.chandrasekaranNOviSPAM@WIPRO.COM.INVALID>

164. upload / download files -- variable size Version 6.12, Windoze t o Unix
     • upload / download files -- variable size Version 6.12, Windoze t o Unix (31 lines)
       From: rpresley <rpresley@GMCF.ORG>

165. variable selection in proc mixed and growth curves
     • variable selection in proc mixed and growth curves (65 lines)
       From: LM <lm@LM.COM>

166. when is says "ERROR: Start is greater than end: -."
     • when is says "ERROR: Start is greater than end: -." (18 lines)
       From: Toni Zhang <thesis8@HOTMAIL.COM>
     • Re: when is says "ERROR: Start is greater than end: -." (53 lines)
       From: Paul Dorfman <paul_dorfman@HOTMAIL.COM>
     • Re: when is says "ERROR: Start is greater than end: -." (42 lines)
       From: dkb@CIX.COMPULINK.CO.UK
     • Re: when is says "ERROR: Start is greater than end: -." (77 lines)
       From: Greg Woolridge <greg.woolridge@TAP.COM>