Table of contents:

• <No subject> (2 messages)
• A _stupid student_ question (6 messages)
• A donwload-macro question
• AF-upperCase attribute... (2 messages)
• Age doesnt matter.
• BUSINESS ASSISTANCE FOR URGENT RELOCATION.
• Be here soon (2 messages)
• Bonjour!
• Bootstrapping for regression analyses (3 messages)
• CHARACTER TO NUMERIC CONVERSION (2 messages)
• CSV-heading using proc export (2 messages)
• Calling a macro with different parameters (7 messages)
• Can anyone pls answer these questions (5 messages)
• Can rxparse be useful for this address cleaning work?? (4 messages)
• Constraints Information (7 messages)
• Creating a specific dataset (2 messages)
• Data Input Problem
• Data Input Problem 2 (6 messages)
• Data reformat to use Proc Tabulate? (3 messages)
• Default values (2 messages)
• Don Henderson (2 messages)
• Download -macro problem (solved)
• Drop out items canceling out
• Drop out items cancelling out (13 messages)
• EXCEL FILES (2 messages)
• Error with Oracle connectivity from SAS (2 messages)
• Excel XP and SAS DDE (4 messages)
• FW: Footnote wont warp
• FW: SAS and Model 204
• FW: scores= option in proc freq
• FYI: pittfalls of data step loop (3 messages)
• Finding Duplicates (7 messages)
• Format Problem (2 messages)
• Format in PROC FREQ (4 messages)
• Formatting problem in alternate line in Proc Report (2 messages)
• Free Animal Sex clip online
• Fwd: PPS sampling
• GREAT BENEFITS
• Get Names of Datasets from Library & Proc SQL (2 messages)
• Getting a copy of SAS to learn the language (2 messages)
• Good Job: Statistical Programmer
• Graphing data....
• HOW TO INSERT A BLANK LINE IN A REPORT WITHIN A VARIABLE VALUE
• Help with data..
• Hey! (3 messages)
• How can I create these variables (7 messages)
• How does SAS deal with missing value of the ByVariable in mer ging
• How does SAS deal with missing value of the ByVariable in merging (4 messages)
• How to insert a line in proc report in a given variable (3 messages)
• How to read UNICODE-encoded data on UNIX SAS V8.2 (2 messages)
• How to set default values
• How to use PROC PLOT
• I don't get %sysexec (5 messages)
• I hate it!
• Inserting values into Excel (2 messages)
• Is Anybody Using SAS Data Warehouse Administrator
• It's your life....
• Iteratively re-weighted least squares (2 messages)
• Just what do you need?
• LOTUS NOTES/PAGE BREAKS
• Last Day of Quarter Loop Problem (10 messages)
• Macro quoting and quoted string length (3 messages)
• Macro reference with total counts at the END (6 messages)
• March SESUG'04 Reminder
• Meta-analysis with PROC MIXED
• Mining a report (4 messages)
• Miracles do happen....
• NESUG 2004 Call for Papers is here !
• NJ SAS Users Group Meeting Friday, March 12
• NJ SAS Users Group Meeting This Friday
• Nested Loop: "v8.2 is about 5x _slower_ than v9.1" (2 messages)
• Nested Loop: "v8.2 is about 5x _slower_ than v9.1" (was Super Size ...)
• New job in UK: Modelling and Simulation statisticians for Gambling industry, suit Academics or Mathematicians (4 messages)
• Newby SAS Enterprise Question (3 messages)
• Normal Distribution Function (4 messages)
• Numeric Questions? (5 messages)
• ODBC (3 messages)
• ODS,Proc Report, Proc Template help
• OT (was:RE: New job in UK: Modelling and Simulation statisticians f orGambling industry, suit Academics or Mathematicians) (4 messages)
• PPS sampling
• PROC BOXPLOT: to be or not to be? (2 messages)
• PROC DATASTEPS (3 messages)
• PROC PRINTTO versus ODS to HTML for Excel
• Please come..
• Problems installing SAS V8.2 (2 messages)
• Proc REPORT, how do I keep things together on a page (2 messages)
• Proof!
• RE : SQL error
• Re; why get Vi,agra when you can get ,super Vi'agra xqobntarltp
• Read Excel into SAS
• Reading files- using file pointers
• Resolved thanks. : Creating a specific dataset
• Returned due to virus; was:Re: Your archive
• Running a VBA macro using DDE (3 messages)
• Running a VBA macro using DDE -- additional reference
• SAS DATE to day-of-week conversion (6 messages)
• SAS Merge - New boy question (8 messages)
• SAS Professional Guild [was RE : Any experience ?]
• SAS Sytem Viewer Variables View
• SAS and Model 204 (3 messages)
• SAS version releases (7 messages)
• SAS/CONNECT and html (3 messages)
• SASAUTOS Question? (11 messages)
• SASOfficeWizard was: Re:VERSION 9: The Big Picture? (2 messages)
• SET Statement with KEY= and Composite Numeric Key (6 messages)
• SORTEDBY after MERGE (4 messages)
• SPSS 11.5 Data Editor: 'Freeze' variables? (2 messages)
• SQL error (4 messages)
• SUGI 29: 366 reasons to attend
• Selecting certain cases (8 messages)
• Setting up a user interface (4 messages)
• Simple Arithmetic question.. (4 messages)
• Simulating Spatial data sets using SAS
• Spring time! (2 messages)
• Stratified random sample using arrays (3 messages)
• Substring Puzzle (12 messages)
• Super Size Dataset from Cartesian Join (11 messages)
• TIP: %IF Outside of Macro
• Temporary Character Array is Cutoff (4 messages)
• Test
• Testing
• Time formatted field in Frame v8.2 (2 messages)
• Transpose Obs into Variables (3 messages)
• Turnbull survival estimation - test of equality of strata?
• UNSUBSCRIBE (5 messages)
• Unix commands in SAS (3 messages)
• Urgent: 5000 Euro Reward (0.09929116184947906)
• VERSION 9: The Big Picture? (10 messages)
• WEEKEND VIAGRA
• What are you gonna do with the new you?
• What's wrong with this: street_n=addr1_1|" "||addr2||" "||addr3||" "||addr4||" "||addr5
• Why DATEPART function is not working (5 messages)
• Will you be here?
• Writing hyperlinks to Excel with SAS (8 messages)
• Z2. Format (4 messages)
• [SAS license assessment] Attention Toronto area SAS users
• [v9] using hashes to merge data (2 messages)
• apologies
• canonical analysis outside of proc rsreg
• changing default of character variable ; was Substring Puzzle
• colapse several records into one (10 messages)
• compare records in two tables (7 messages)
• compare records in two tables - clarification (3 messages)
• dataset conversion from v6 to v8 (10 messages)
• detecting changes in data
• finding location in input statement (7 messages)
• gprobcnt
• help to find the logic (2 messages)
• help with an error message (2 messages)
• how to use sql coalesce with time (9 messages)
• ignore this ..this is just a test mail
• lag Return upto 12 time for unbalanced panel (3 messages)
• lag function (4 messages)
• look for a simple way to define a macro variable (7 messages)
• macro help routines
• no growth then money back and u keep..
• odbc problem (2 messages)
• output sum of vars to a file
• pittfalls of data step loop
• proc appsrv et al (3 messages)
• proc lifetest plots=(h) doesn`t work (2 messages)
• proc regression macro ..
• proc sql question (2 messages)
• read the first 3 digit of the 4-digit data (4 messages)
• remove (2 messages)
• reply fast
• report question (2 messages)
• tip macro Put_ (8 messages)
• truncated values in sashelp.vmacro
• u might want to see this
• unsubscribe
• variable clarification (3 messages)
• what's the cmd for canceling submitted statements? (3 messages)
• zero truncated poisson regression (3 messages)

1. <No subject>
   • <No subject> (82 lines)
     From: Peter Crawford <peter@CRAWFORDSOFTWARE.DEMON.CO.UK>
   • <No subject> (49 lines)
     From: Ian Whitlock <iw1junk@COMCAST.NET>

2. A _stupid student_ question
   • Re: A _stupid student_ question (83 lines)
     From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
   • Re: A _stupid student_ question (68 lines)
     From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
   • Re: A _stupid student_ question (95 lines)
     From: Lars Wahlgren <lars.wahlgren.pleasenospam@STAT.LU.SE>
   • Re: A _stupid student_ question (79 lines)
     From: Philip_Crane@WORKCOVER.VIC.GOV.AU
   • Re: A _stupid student_ question (56 lines)
     From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
   • A _stupid student_ question (50 lines)
     From: Vera <vzamniborsch@HOTMAIL.COM>

3. A donwload-macro question
   • A donwload-macro question (187 lines)
     From: GOMEZ TEJERINA, PEDRO ALBERTO <PEDRO.GOMEZ@GRUPOBBVA.COM>

4. AF-upperCase attribute...
   • Re: AF-upperCase attribute... (27 lines)
     From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
   • AF-upperCase attribute... (13 lines)
     From: rmengis@YCI.COM

5. Age doesnt matter.
   • Age doesnt matter. (20 lines)
     From: Olivia Gagnon <oliviagagnon_kk@HOTMAIL.COM>

6. BUSINESS ASSISTANCE FOR URGENT RELOCATION.
   • BUSINESS ASSISTANCE FOR URGENT RELOCATION. (40 lines)
     From: adamswell1 <adamswell1@TELSTRA.COM>

7. Be here soon
   • Be here soon (18 lines)
     From: Nathan Melton <nathanmeltonrs@ALTIUM.NL>
   • Be here soon (41 lines)
     From: Sandra K. Wyatt <sandrakwyatt_nd@HOTMAIL.COM>

8. Bonjour!
   • Bonjour! (37 lines)
     From: Ana Dejesus <dejesusnk@HOTMAIL.COM>

9. Bootstrapping for regression analyses
   • Re: Bootstrapping for regression analyses (54 lines)
     From: Daniel Ward <daward2@VT.EDU>
   • Re: Bootstrapping for regression analyses (52 lines)
     From: Paul Thompson <paul@WUBIOS.WUSTL.EDU>
   • Bootstrapping for regression analyses (44 lines)
     From: Peter Flom <flom@NDRI.ORG>

10. CHARACTER TO NUMERIC CONVERSION
    • Re: CHARACTER TO NUMERIC CONVERSION (53 lines)
      From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
    • CHARACTER TO NUMERIC CONVERSION (35 lines)
      From: Tonkovich, Mike <Mike.Tonkovich@DNR.STATE.OH.US>

11. CSV-heading using proc export
    • Re: CSV-heading using proc export (61 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
    • CSV-heading using proc export (19 lines)
      From: taran gujral <taran_jit@YAHOO.COM>

12. Calling a macro with different parameters
    • Re: Calling a macro with different parameters (14 lines)
      From: Mikko Myrskyla <mikko.myrskyla@HELSINKI.FI>
    • Re: Calling a macro with different parameters (47 lines)
      From: chris <fast_rabbit@GMX.CH>
    • Re: Calling a macro with different parameters (63 lines)
      From: Tarbash Patel a.k.a. Babu <epidemiologist@SCIENTIST.COM>
    • Re: Calling a macro with different parameters (79 lines)
      From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
    • Re: Calling a macro with different parameters (66 lines)
      From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
    • Re: Calling a macro with different parameters (49 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
    • Calling a macro with different parameters (33 lines)
      From: Mikko Myrskyla <mikko.myrskyla@HELSINKI.FI>

13. Can anyone pls answer these questions
    • Re: Can anyone pls answer these questions (41 lines)
      From: Lou <lpogodajr292185@COMCAST.NET>
    • Re: Can anyone pls answer these questions (16 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Can anyone pls answer these questions (36 lines)
      From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
    • Re: Can anyone pls answer these questions (30 lines)
      From: Tom <e_to_the_i_pi@HOTMAIL.COM>
    • Can anyone pls answer these questions (14 lines)
      From: Mahesh <umamaheshbabuk@REDIFFMAIL.COM>

14. Can rxparse be useful for this address cleaning work??
    • Re: Can rxparse be useful for this address cleaning work?? (99 lines)
      From: Duck-Hye Yang <dyang@CHAPINHALL.ORG>
    • Re: Can rxparse be useful for this address cleaning work?? (80 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
    • Re: Can rxparse be useful for this address cleaning work?? (85 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
    • Can rxparse be useful for this address cleaning work?? (40 lines)
      From: Duck-Hye Yang <dyang@CHAPINHALL.ORG>

15. Constraints Information
    • Re: Constraints Information (104 lines)
      From: Nitin Chandak <nitin.chandak@GLOBALCASE.NET>
    • Re: Constraints Information (97 lines)
      From: Nitin Chandak <nitin.chandak@GLOBALCASE.NET>
    • Re: Constraints Information (92 lines)
      From: Nitin Chandak <nitin.chandak@GLOBALCASE.NET>
    • Re: Constraints Information (69 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: Constraints Information (70 lines)
      From: Randy Herbison <RandyHerbison@WESTAT.COM>
    • Re: Constraints Information (76 lines)
      From: Xavier Autret <xav_x@NOOS.FR>
    • Constraints Information (54 lines)
      From: Nitin Chandak <nitin.chandak@GLOBALCASE.NET>

16. Creating a specific dataset
    • Re: Creating a specific dataset (68 lines)
      From: Barry Schwarz <schwarzb@DELOZ.NET>
    • Creating a specific dataset (52 lines)
      From: seema <wormpai@HOTMAIL.COM>

17. Data Input Problem
    • Data Input Problem (255 lines)
      From: Ken <1800okla@HANMAIL.NET>

18. Data Input Problem 2
    • Re: Data Input Problem 2 (94 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
    • Re: Data Input Problem 2 (76 lines)
      From: steve <bittnerse@YAHOO.COM>
    • Re: Data Input Problem 2 (104 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Data Input Problem 2 (106 lines)
      From: pudding man <pudding_man@MAIL.COM>
    • Re: Data Input Problem 2 (83 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Data Input Problem 2 (55 lines)
      From: Ken Gim <1800okla@HANMAIL.NET>

19. Data reformat to use Proc Tabulate?
    • Re: Data reformat to use Proc Tabulate? (79 lines)
      From: DePuy, Venita <depuy001@DCRI.DUKE.EDU>
    • Re: Data reformat to use Proc Tabulate? (52 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Data reformat to use Proc Tabulate? (41 lines)
      From: DePuy, Venita <depuy001@DCRI.DUKE.EDU>

20. Default values
    • Re: Default values (66 lines)
      From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
    • Default values (41 lines)
      From: Nitin Chandak <nitin.chandak@GLOBALCASE.NET>

21. Don Henderson
    • Re: Don Henderson (26 lines)
      From: Paul Kairis <kairis@COX.NET>
    • Don Henderson (13 lines)
      From: Charles Patridge <charles_s_patridge@PRODIGY.NET>

22. Download -macro problem (solved)
    • Download -macro problem (solved) (105 lines)
      From: GOMEZ TEJERINA, PEDRO ALBERTO <PEDRO.GOMEZ@GRUPOBBVA.COM>

23. Drop out items canceling out
    • Re: Drop out items canceling out (18 lines)
      From: Fuchs, Tom <Tom.Fuchs@LGEENERGY.COM>

24. Drop out items cancelling out
    • Re: Drop out items cancelling out (176 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Drop out items cancelling out (183 lines)
      From: Robert Burbidge <RBurbidge@PHD.CO.UK>
    • Re: Drop out items cancelling out (33 lines)
      From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
    • Re: Drop out items cancelling out (156 lines)
      From: Robert Burbidge <RBurbidge@PHD.CO.UK>
    • Re: Drop out items cancelling out (123 lines)
      From: PD <sophe88@YAHOO.COM>
    • Re: Drop out items cancelling out (54 lines)
      From: Michael Mace <michael_mace@GOODYEAR.COM>
    • Re: Drop out items cancelling out (137 lines)
      From: KrzysOPoranku <krzysoporanku@INTERIA.PL>
    • Re: Drop out items cancelling out (104 lines)
      From: Robert Burbidge <RBurbidge@PHD.CO.UK>
    • Re: Drop out items cancelling out (205 lines)
      From: Terjeson, Mark <TERJEM@DSHS.WA.GOV>
    • Re: Drop out items cancelling out (93 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
    • Re: Drop out items cancelling out (91 lines)
      From: Terjeson, Mark <TERJEM@DSHS.WA.GOV>
    • Re: Drop out items cancelling out (56 lines)
      From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
    • Drop out items cancelling out (33 lines)
      From: PD <sophe88@YAHOO.COM>

25. EXCEL FILES
    • Re: EXCEL FILES (31 lines)
      From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL>
    • EXCEL FILES (16 lines)
      From: Edward Gano <Edward_Gano@AHM.HONDA.COM>

26. Error with Oracle connectivity from SAS
    • Re: Error with Oracle connectivity from SAS (59 lines)
      From: Nancy Brucken <brucken@PROVIDE.NET>
    • Error with Oracle connectivity from SAS (36 lines)
      From: Steve Zelasky <sas_learner2000@YAHOO.COM>

27. Excel XP and SAS DDE
    • Re: Excel XP and SAS DDE (38 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
    • Re: Excel XP and SAS DDE (19 lines)
      From: Bobby Kidd <rakidd@FTB.COM>
    • Re: Excel XP and SAS DDE (100 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
    • Excel XP and SAS DDE (81 lines)
      From: Bobby Kidd <rakidd@FTB.COM>

28. FW: Footnote wont warp
    • FW: Footnote wont warp (44 lines)
      From: Igor Kurbeko <ikurbeko@ATHEROGENICS.COM>

29. FW: SAS and Model 204
    • FW: SAS and Model 204 (39 lines)
      From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM>

30. FW: scores= option in proc freq
    • FW: scores= option in proc freq (18 lines)
      From: Deborah Wentworth <Deborah.Wentworth@ACORNCV.COM>

31. FYI: pittfalls of data step loop
    • Re: FYI: pittfalls of data step loop (70 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: FYI: pittfalls of data step loop (109 lines)
      From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
    • FYI: pittfalls of data step loop (55 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>

32. Finding Duplicates
    • Re: Finding Duplicates (20 lines)
      From: Charles Patridge <charles_s_patridge@PRODIGY.NET>
    • Re: Finding Duplicates (62 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Finding Duplicates (133 lines)
      From: Tim Wade <wade_tj@YAHOO.COM>
    • Re: Finding Duplicates (65 lines)
      From: Farrer, Andrew C <Andrew.Farrer@CIBC.COM>
    • Re: Finding Duplicates (48 lines)
      From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL>
    • Re: Finding Duplicates (70 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
    • Finding Duplicates (35 lines)
      From: Toigo, Melissa L. <mtoigo@OXHP.COM>

33. Format Problem
    • Re: Format Problem (111 lines)
      From: Stephen Dunn <stephen.dunn@HIGHWAY-INSURANCE.CO.UK>
    • Re: Format Problem (103 lines)
      From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>

34. Format in PROC FREQ
    • Re: Format in PROC FREQ (25 lines)
      From: Yanal Ansouqa <ansouqa@SBCGLOBAL.NET>
    • Re: Format in PROC FREQ (29 lines)
      From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
    • Re: Format in PROC FREQ (30 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
    • Format in PROC FREQ (19 lines)
      From: Pascale Beaupré <Pascale.Beaupre@STATCAN.CA>

35. Formatting problem in alternate line in Proc Report
    • Re: Formatting problem in alternate line in Proc Report (212 lines)
      From: Anbu <aarumugam@STTHOMAS.EDU>
    • Re: Formatting problem in alternate line in Proc Report (204 lines)
      From: Anbu <aarumugam@STTHOMAS.EDU>

36. Free Animal Sex clip online
    • Free Animal Sex clip online (38 lines)
      From: Susanne Alvarado <alvarado_tv@EXCITE.COM>

37. Fwd: PPS sampling
    • Fwd: PPS sampling (42 lines)
      From: Zhonghe Li <zli@HSPH.HARVARD.EDU>

38. GREAT BENEFITS
    • GREAT BENEFITS (42 lines)
      From: adamswellington75 <adamswellington75@TELSTRA.COM>

39. Get Names of Datasets from Library & Proc SQL
    • Re: Get Names of Datasets from Library & Proc SQL (72 lines)
      From: Dennis Diskin <diskin.dennis@KENDLE.COM>
    • Get Names of Datasets from Library & Proc SQL (49 lines)
      From: Dubravko Dolic <dubro@DOLIC.DE>

40. Getting a copy of SAS to learn the language
    • Re: Getting a copy of SAS to learn the language (190 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: Getting a copy of SAS to learn the language (52 lines)
      From: lpogoda <lpogoda@HOTMAIL.COM>

41. Good Job: Statistical Programmer
    • Good Job: Statistical Programmer (20 lines)
      From: Chris Holland <pch1969@YAHOO.COM>

42. Graphing data....
    • Graphing data.... (43 lines)
      From: Richard N. Heyliger <rheyliger@KEYSPANENERGY.COM>

43. HOW TO INSERT A BLANK LINE IN A REPORT WITHIN A VARIABLE VALUE
    • HOW TO INSERT A BLANK LINE IN A REPORT WITHIN A VARIABLE VALUE (34 lines)
      From: sas programmer <sasprogrammer@HOTMAIL.COM>

44. Help with data..
    • Re: Help with data.. (24 lines)
      From: Fco.Javier de Castro <jdcastro@INE.ES>

45. Hey!
    • Hey! (18 lines)
      From: Terrance Lozano <terrancelozanoyy@EXCITE.COM>
    • Hey! (18 lines)
      From: Luisa F. Klein <l.klein_ec@YAHOO.COM>
    • Hey! (19 lines)
      From: Carly Richey <richey_hw@ATD-CLAN.DE>

46. How can I create these variables
    • Re: How can I create these variables (132 lines)
      From: Scott <usenet739_yahoo_com_au@CRONKITE.CC.UGA.EDU>
    • Re: How can I create these variables (111 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: How can I create these variables (124 lines)
      From: Robert Burbidge <RBurbidge@PHD.CO.UK>
    • Re: How can I create these variables (107 lines)
      From: Scott <usenet739_yahoo_com_au@CRONKITE.CC.UGA.EDU>
    • Re: How can I create these variables (85 lines)
      From: Don Stanley <don_stanley@PARADISE.NET.NZ>
    • Re: How can I create these variables (73 lines)
      From: Bittner, Stephen <Stephen.Bittner@CAREMARK.COM>
    • How can I create these variables (29 lines)
      From: Joy <mayue72@HOTMAIL.COM>

47. How does SAS deal with missing value of the ByVariable in mer ging
    • Re: How does SAS deal with missing value of the ByVariable in mer ging (43 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>

48. How does SAS deal with missing value of the ByVariable in merging
    • Re: How does SAS deal with missing value of the ByVariable in merging (66 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: How does SAS deal with missing value of the ByVariable in merging (59 lines)
      From: Lou <lpogodajr292185@COMCAST.NET>
    • Re: How does SAS deal with missing value of the ByVariable in merging (58 lines)
      From: Dennis Diskin <diskin.dennis@KENDLE.COM>
    • How does SAS deal with missing value of the ByVariable in merging (20 lines)
      From: 0101 htns <htns0101@YAHOO.COM>

49. How to insert a line in proc report in a given variable
    • Re: How to insert a line in proc report in a given variable (61 lines)
      From: Don & Susann <don_stanley@PARADISE.NET.NZ>
    • Re: How to insert a line in proc report in a given variable (74 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
    • How to insert a line in proc report in a given variable (42 lines)
      From: sas programmer <sasprogrammer@HOTMAIL.COM>

50. How to read UNICODE-encoded data on UNIX SAS V8.2
    • Re: How to read UNICODE-encoded data on UNIX SAS V8.2 (26 lines)
      From: Evert Carton <me@YOU.HE>
    • How to read UNICODE-encoded data on UNIX SAS V8.2 (14 lines)
      From: Jan <jan@SELCHAU-HANSEN.DK>

51. How to set default values
    • How to set default values (40 lines)
      From: Nitin Chandak <nitin.chandak@GLOBALCASE.NET>

52. How to use PROC PLOT
    • How to use PROC PLOT (72 lines)
      From: Mark T. Regan, K8MTR <netsfw_sysprog@YAHOO.COM>

53. I don't get %sysexec
    • Re: I don't get %sysexec (46 lines)
      From: Stuart Luppescu <s-luppescu@UCHICAGO.EDU>
    • Re: I don't get %sysexec (35 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
    • Re: I don't get %sysexec (67 lines)
      From: Don Stanley <don_stanley@PARADISE.NET.NZ>
    • Re: I don't get %sysexec (24 lines)
      From: Stuart Luppescu <s-luppescu@UCHICAGO.EDU>
    • I don't get %sysexec (42 lines)
      From: Stuart Luppescu <s-luppescu@UCHICAGO.EDU>

54. I hate it!
    • I hate it! (21 lines)
      From: Maryann Benton <maryannbentonco@ALLEGRO.NO>

55. Inserting values into Excel
    • Re: Inserting values into Excel (117 lines)
      From: Bittner, Stephen <Stephen.Bittner@CAREMARK.COM>
    • Inserting values into Excel (90 lines)
      From: Anbu Arasu <aarumugam@STTHOMAS.EDU>

56. Is Anybody Using SAS Data Warehouse Administrator
    • Is Anybody Using SAS Data Warehouse Administrator (32 lines)
      From: John F. Regus <jfregus@IX.NETCOM.COM>

57. It's your life....
    • It's your life.... (18 lines)
      From: Quinn Bowers <quinn.bowers_tq@BARBARASKITCHEN.CO.UK>

58. Iteratively re-weighted least squares
    • Re: Iteratively re-weighted least squares (98 lines)
      From: Dale McLerran <stringplayer_2@YAHOO.COM>
    • Iteratively re-weighted least squares (31 lines)
      From: david.mcnulty@QUESTINTL.COM

59. Just what do you need?
    • Just what do you need? (38 lines)
      From: Trina Bowling <trinabowling_ez@HOTMAIL.COM>

60. LOTUS NOTES/PAGE BREAKS
    • LOTUS NOTES/PAGE BREAKS (37 lines)
      From: Edward Gano <Edward_Gano@AHM.HONDA.COM>

61. Last Day of Quarter Loop Problem
    • Re: Last Day of Quarter Loop Problem (73 lines)
      From: Lou <lpogodajr292185@COMCAST.NET>
    • Re: Last Day of Quarter Loop Problem (235 lines)
      From: Ian Whitlock <iw1junk@COMCAST.NET>
    • Re: Last Day of Quarter Loop Problem (108 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
    • Re: Last Day of Quarter Loop Problem (18 lines)
      From: Rick <xderrida@YAHOO.COM>
    • Re: Last Day of Quarter Loop Problem (87 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Last Day of Quarter Loop Problem (262 lines)
      From: Glenn Heagerty <gheagerty@EARTHLINK.NET>
    • Re: Last Day of Quarter Loop Problem (21 lines)
      From: Rick <xderrida@YAHOO.COM>
    • Re: Last Day of Quarter Loop Problem (92 lines)
      From: Don Stanley <don_stanley@PARADISE.NET.NZ>
    • Re: Last Day of Quarter Loop Problem (12 lines)
      From: Don Stanley <don_stanley@PARADISE.NET.NZ>
    • Last Day of Quarter Loop Problem (80 lines)
      From: Rick <xderrida@YAHOO.COM>

62. Macro quoting and quoted string length
    • Re: Macro quoting and quoted string length (27 lines)
      From: Bruce Bradbury <BruceBrad@INAME.COM>
    • Re: Macro quoting and quoted string length (64 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
    • Re: Macro quoting and quoted string length (94 lines)
      From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>

63. Macro reference with total counts at the END
    • Re: Macro reference with total counts at the END (180 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Macro reference with total counts at the END (113 lines)
      From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>
    • Re: Macro reference with total counts at the END (136 lines)
      From: PD <sophe88@YAHOO.COM>
    • Re: Macro reference with total counts at the END (89 lines)
      From: Dennis Diskin <diskin.dennis@KENDLE.COM>
    • Re: Macro reference with total counts at the END (130 lines)
      From: Scott <usenet739_yahoo_com_au@CRONKITE.CC.UGA.EDU>
    • Macro reference with total counts at the END (65 lines)
      From: PD <sophe88@YAHOO.COM>

64. March SESUG'04 Reminder
    • March SESUG'04 Reminder (31 lines)
      From: SESUG INFORMATION <sesuginc@UGA.EDU>

65. Meta-analysis with PROC MIXED
    • Meta-analysis with PROC MIXED (34 lines)
      From: Mike Cheung <mikewlcheung@YAHOO.COM>

66. Mining a report
    • Re: Mining a report (193 lines)
      From: Nori Abakah <moree@BRAATPAQ.COM>
    • Re: Mining a report (20 lines)
      From: Roy@HOME.NOT
    • Re: Mining a report (116 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Mining a report (105 lines)
      From: Nori Abakah <moree@BRAATPAQ.COM>

67. Miracles do happen....
    • Miracles do happen.... (19 lines)
      From: Vicki I. Trevino <vi.trevino_ef@ALTENDORFER.AT>

68. NESUG 2004 Call for Papers is here !
    • NESUG 2004 Call for Papers is here ! (60 lines)
      From: Ray Pass <raypass@ATT.NET>

69. NJ SAS Users Group Meeting Friday, March 12
    • NJ SAS Users Group Meeting Friday, March 12 (44 lines)
      From: Vittas, Ted <Ted.Vittas@CENDANT.COM>

70. NJ SAS Users Group Meeting This Friday
    • NJ SAS Users Group Meeting This Friday (39 lines)
      From: Vittas, Ted <Ted.Vittas@CENDANT.COM>

71. Nested Loop: "v8.2 is about 5x _slower_ than v9.1"
    • Re: Nested Loop: "v8.2 is about 5x _slower_ than v9.1" (55 lines)
      From: pudding man <pudding_man@MAIL.COM>
    • Re: Nested Loop: "v8.2 is about 5x _slower_ than v9.1" (313 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

72. Nested Loop: "v8.2 is about 5x _slower_ than v9.1" (was Super Size ...)
    • Nested Loop: "v8.2 is about 5x _slower_ than v9.1" (was Super Size ...) (153 lines)
      From: pudding man <pudding_man@MAIL.COM>

73. New job in UK: Modelling and Simulation statisticians for Gambling industry, suit Academics or Mathematicians
    • Re: New job in UK: Modelling and Simulation statisticians for Gambling industry, suit Academics or Mathematicians (22 lines)
      From: Lars Wahlgren <lars.wahlgren.pleasenospam@STAT.LU.SE>
    • Re: New job in UK: Modelling and Simulation statisticians for Gambling industry, suit Academics or Mathematicians (68 lines)
      From: Robert Burbidge <RBurbidge@PHD.CO.UK>
    • Re: New job in UK: Modelling and Simulation statisticians for Gambling industry, suit Academics or Mathematicians (13 lines)
      From: Charles Patridge <charles_s_patridge@PRODIGY.NET>
    • New job in UK: Modelling and Simulation statisticians for Gambling industry, suit Academics or Mathematicians (39 lines)
      From: Natalie Fforde <natalie@FFORDE-MANAGEMENT.COM>

74. Newby SAS Enterprise Question
    • Re: Newby SAS Enterprise Question (55 lines)
      From: Van Bain <vanirex@TELEPORT.COM>
    • Re: Newby SAS Enterprise Question (44 lines)
      From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU>
    • Newby SAS Enterprise Question (17 lines)
      From: Van Bain <william.van.bain@HP.COM>

75. Normal Distribution Function
    • Re: Normal Distribution Function (59 lines)
      From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
    • Re: Normal Distribution Function (69 lines)
      From: rdporto1 <rdporto1@TERRA.COM.BR>
    • Re: Normal Distribution Function (33 lines)
      From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
    • Normal Distribution Function (21 lines)
      From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>

76. Numeric Questions?
    • Re: Numeric Questions? (31 lines)
      From: Michael S. Zdeb <msz03@HEALTH.STATE.NY.US>
    • Re: Numeric Questions? (62 lines)
      From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
    • Re: Numeric Questions? (50 lines)
      From: Dennis Diskin <diskin.dennis@KENDLE.COM>
    • Re: Numeric Questions? (32 lines)
      From: Roger Lustig <trovato@VERIZON.NET>
    • Numeric Questions? (18 lines)
      From: Ross, Michael D <michael.ross@ASTRAZENECA.COM>

77. ODBC
    • Re: ODBC (84 lines)
      From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
    • Re: ODBC (75 lines)
      From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM>
    • ODBC (18 lines)
      From: Mai To <Mai.To@UTH.TMC.EDU>

78. ODS,Proc Report, Proc Template help
    • ODS,Proc Report, Proc Template help (116 lines)
      From: Sterling Price <Sterling.Price@WAL-MART.COM>

79. OT (was:RE: New job in UK: Modelling and Simulation statisticians f orGambling industry, suit Academics or Mathematicians)
    • Re: OT (was:RE: New job in UK: Modelling and Simulation statisticians f orGambling industry, suit Academics or Mathematicians) (76 lines)
      From: 0101 htns <htns0101@YAHOO.COM>
    • Re: OT (was:RE: New job in UK: Modelling and Simulation statisticians f orGambling industry, suit Academics or Mathematicians) (70 lines)
      From: William W. Viergever <wwvierg@ATTGLOBAL.NET>
    • Re: OT (was:RE: New job in UK: Modelling and Simulation statisticians f orGambling industry, suit Academics or Mathematicians) (42 lines)
      From: Venky Chakravarthy <venky.chakravarthy@PFIZER.COM>
    • OT (was:RE: New job in UK: Modelling and Simulation statisticians f orGambling industry, suit Academics or Mathematicians) (35 lines)
      From: Boylan, David <DBoylan@HRBLOCK.COM>

80. PPS sampling
    • PPS sampling (20 lines)
      From: Zhonghe Li <zli@HSPH.HARVARD.EDU>

81. PROC BOXPLOT: to be or not to be?
    • Re: PROC BOXPLOT: to be or not to be? (26 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
    • PROC BOXPLOT: to be or not to be? (33 lines)
      From: simon <limonade84@YAHOO.COM>

82. PROC DATASTEPS
    • Re: PROC DATASTEPS (7 lines)
      From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
    • Re: PROC DATASTEPS (39 lines)
      From: Dennis Diskin <diskin.dennis@KENDLE.COM>
    • PROC DATASTEPS (16 lines)
      From: dharmadam <dharmadam_man@HOTMAIL.COM>

83. PROC PRINTTO versus ODS to HTML for Excel
    • PROC PRINTTO versus ODS to HTML for Excel (21 lines)
      From: Myra Oltsik <my_sas_spot@YAHOO.COM>

84. Please come..
    • Please come.. (37 lines)
      From: Luella C. Boyer <l_boyerby@9BIT.QC.CA>

85. Problems installing SAS V8.2
    • Re: Problems installing SAS V8.2 (25 lines)
      From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
    • Problems installing SAS V8.2 (17 lines)
      From: emmanuel.perray@MPSA.COM

86. Proc REPORT, how do I keep things together on a page
    • Re: Proc REPORT, how do I keep things together on a page (114 lines)
      From: Don Stanley <don_stanley@PARADISE.NET.NZ>
    • Proc REPORT, how do I keep things together on a page (93 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

87. Proof!
    • Proof! (19 lines)
      From: Latasha Farmer <latashafarmer_dr@HOTMAIL.COM>

88. RE : SQL error
    • RE : SQL error (145 lines)
      From: Datametric <datametric@CLUB-INTERNET.FR>

89. Re; why get Vi,agra when you can get ,super Vi'agra xqobntarltp
    • Re; why get Vi,agra when you can get ,super Vi'agra xqobntarltp (35 lines)
      From: Edmond Guerrero <eguerrerosh@METLA.FI>

90. Read Excel into SAS
    • Re: Read Excel into SAS (21 lines)
      From: Tarbash Patel a.k.a. Babu <epidemiologist@SCIENTIST.COM>

91. Reading files- using file pointers
    • Reading files- using file pointers (18 lines)
      From: taran gujral <taran_jit@YAHOO.COM>

92. Resolved thanks. : Creating a specific dataset
    • Resolved thanks. : Creating a specific dataset (54 lines)
      From: seema <wormpai@HOTMAIL.COM>

93. Returned due to virus; was:Re: Your archive
    • Returned due to virus; was:Re: Your archive (12 lines)
      From: SAS-L@VM.MARIST.EDU

94. Running a VBA macro using DDE
    • Re: Running a VBA macro using DDE (55 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
    • Re: Running a VBA macro using DDE (70 lines)
      From: Nat Wooding <Nathaniel_Wooding@DOM.COM>
    • Running a VBA macro using DDE (38 lines)
      From: Kevin Roland Viel <kviel@EMORY.EDU>

95. Running a VBA macro using DDE -- additional reference
    • Re: Running a VBA macro using DDE -- additional reference (70 lines)
      From: Nat Wooding <Nathaniel_Wooding@DOM.COM>

96. SAS DATE to day-of-week conversion
    • Re: SAS DATE to day-of-week conversion (79 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: SAS DATE to day-of-week conversion (23 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
    • Re: SAS DATE to day-of-week conversion (102 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
    • Re: SAS DATE to day-of-week conversion (58 lines)
      From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
    • Re: SAS DATE to day-of-week conversion (24 lines)
      From: 0101 htns <htns0101@YAHOO.COM>
    • SAS DATE to day-of-week conversion (14 lines)
      From: Tonkovich, Mike <Mike.Tonkovich@DNR.STATE.OH.US>

97. SAS Merge - New boy question
    • Re: SAS Merge - New boy question (134 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: SAS Merge - New boy question (15 lines)
      From: Fco.Javier de Castro <jdcastro@INE.ES>
    • Re: SAS Merge - New boy question (83 lines)
      From: Dennis Diskin <diskin.dennis@KENDLE.COM>
    • Re: SAS Merge - New boy question (47 lines)
      From: Robert Burbidge <RBurbidge@PHD.CO.UK>
    • Re: SAS Merge - New boy question (140 lines)
      From: Robert Burbidge <RBurbidge@PHD.CO.UK>
    • Re: SAS Merge - New boy question (41 lines)
      From: Gina Nicolosi <ginanicolosi@HOTMAIL.COM>
    • Re: SAS Merge - New boy question (70 lines)
      From: Evert Carton <me@YOU.HE>
    • SAS Merge - New boy question (59 lines)
      From: Richard <richard.lewis@DASA.MOD.UK>

98. SAS Professional Guild [was RE : Any experience ?]
    • SAS Professional Guild [was RE : Any experience ?] (84 lines)
      From: Tanya Kolosova <tanya@WATCHWISE.COM>

99. SAS Sytem Viewer Variables View
    • SAS Sytem Viewer Variables View (22 lines)
      From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM>

100. SAS and Model 204
     • Re: SAS and Model 204 (30 lines)
       From: L. Bertolini <bertolini.1@OSU.EDU>
     • Re: SAS and Model 204 (28 lines)
       From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
     • SAS and Model 204 (20 lines)
       From: DeForke, Michael (DCA) <Michael_DeForke@JUSTEX.NET>

101. SAS version releases
     • Re: SAS version releases (14 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • Re: SAS version releases (53 lines)
       From: mdmiller <mdmiller@SYR.EDU>
     • Re: SAS version releases (43 lines)
       From: Chase, Neil <Neil.Chase@ASTRAZENECA.COM>
     • Re: SAS version releases (30 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: SAS version releases (43 lines)
       From: Mark D. H. Miller <mdmiller@SYR.EDU>
     • Re: SAS version releases (45 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • SAS version releases (21 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>

102. SAS/CONNECT and html
     • Re: SAS/CONNECT and html (19 lines)
       From: Bart Heinsius <eombah@HOTMAIL.COM>
     • Re: SAS/CONNECT and html (77 lines)
       From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK>
     • SAS/CONNECT and html (43 lines)
       From: Stephen Dunn <stephen.dunn@HIGHWAY-INSURANCE.CO.UK>

103. SASAUTOS Question?
     • Re: SASAUTOS Question? (61 lines)
       From: Ross, Michael D <michael.ross@ASTRAZENECA.COM>
     • Re: SASAUTOS Question? (53 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • SASAUTOS Question? (46 lines)
       From: Ian Whitlock <iw1junk@COMCAST.NET>
     • Re: SASAUTOS Question? (62 lines)
       From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
     • Re: SASAUTOS Question? (65 lines)
       From: Ross, Michael D <michael.ross@ASTRAZENECA.COM>
     • Re: SASAUTOS Question? (52 lines)
       From: Ross, Michael D <michael.ross@ASTRAZENECA.COM>
     • Re: SASAUTOS Question? (52 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • Re: SASAUTOS Question? (46 lines)
       From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
     • Re: SASAUTOS Question? (37 lines)
       From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
     • Re: SASAUTOS Question? (35 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • SASAUTOS Question? (29 lines)
       From: Ross, Michael D <michael.ross@ASTRAZENECA.COM>

104. SASOfficeWizard was: Re:VERSION 9: The Big Picture?
     • Re: SASOfficeWizard was: Re:VERSION 9: The Big Picture? (130 lines)
       From: Shawn Edney <Edney.Shawn@EPAMAIL.EPA.GOV>
     • SASOfficeWizard was: Re:VERSION 9: The Big Picture? (72 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>

105. SET Statement with KEY= and Composite Numeric Key
     • Re: SET Statement with KEY= and Composite Numeric Key (72 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • Re: SET Statement with KEY= and Composite Numeric Key (61 lines)
       From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
     • Re: SET Statement with KEY= and Composite Numeric Key (54 lines)
       From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
     • Re: SET Statement with KEY= and Composite Numeric Key (52 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: SET Statement with KEY= and Composite Numeric Key (40 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • SET Statement with KEY= and Composite Numeric Key (19 lines)
       From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>

106. SORTEDBY after MERGE
     • Re: SORTEDBY after MERGE (125 lines)
       From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
     • Re: SORTEDBY after MERGE (119 lines)
       From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
     • Re: SORTEDBY after MERGE (119 lines)
       From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
     • SORTEDBY after MERGE (87 lines)
       From: Robert Burbidge <RBurbidge@PHD.CO.UK>

107. SPSS 11.5 Data Editor: 'Freeze' variables?
     • Re: SPSS 11.5 Data Editor: 'Freeze' variables? (11 lines)
       From: Richard Ristow <wrristow@MINDSPRING.COM>
     • SPSS 11.5 Data Editor: 'Freeze' variables? (24 lines)
       From: Richard Ristow <wrristow@MINDSPRING.COM>

108. SQL error
     • Re: SQL error (168 lines)
       From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
     • Re: SQL error (149 lines)
       From: Don Stanley <don_stanley@PARADISE.NET.NZ>
     • Re: SQL error (132 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • SQL error (117 lines)
       From: Dunn, Toby <tdunn@TEA.STATE.TX.US>

109. SUGI 29: 366 reasons to attend
     • SUGI 29: 366 reasons to attend (15 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>

110. Selecting certain cases
     • Re: Selecting certain cases (24 lines)
       From: jon oneil <saslist@COMCAST.NET>
     • Re: Selecting certain cases (46 lines)
       From: shiling zhang <shiling99@YAHOO.COM>
     • Re: Selecting certain cases (106 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: Selecting certain cases (98 lines)
       From: =?koi8-r?Q?=22?=Paul Dorfman=?koi8-r?Q?=22=20?= <sashole@MAIL.RU>
     • Re: Selecting certain cases (69 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: Selecting certain cases (34 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • Re: Selecting certain cases (59 lines)
       From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
     • Selecting certain cases (21 lines)
       From: saslist@COMCAST.NET

111. Setting up a user interface
     • Re: Setting up a user interface (16 lines)
       From: Charles Patridge <charles_s_patridge@PRODIGY.NET>
     • Re: Setting up a user interface (24 lines)
       From: Charles Patridge <charles_s_patridge@PRODIGY.NET>
     • Re: Setting up a user interface (28 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • Setting up a user interface (17 lines)
       From: McCormick, Mike <Mike.McCormick@THECB.STATE.TX.US>

112. Simple Arithmetic question..
     • Re: Simple Arithmetic question.. (99 lines)
       From: Robert Burbidge <RBurbidge@PHD.CO.UK>
     • Re: Simple Arithmetic question.. (66 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: Simple Arithmetic question.. (64 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • Simple Arithmetic question.. (28 lines)
       From: Christopher Amherst <camherst@MISER.UMASS.EDU>

113. Simulating Spatial data sets using SAS
     • Simulating Spatial data sets using SAS (26 lines)
       From: Song <sounpra@YAHOO.COM>

114. Spring time!
     • Spring time! (38 lines)
       From: Jules McGhee <mcGhee_rd@BOSS.AB.CA>
     • Spring time! (40 lines)
       From: Concetta Preston <c_prestonjg@9ONLINE.FR>

115. Stratified random sample using arrays
     • Re: Stratified random sample using arrays (109 lines)
       From: Ben Powell <Ben.powell@CLA.CO.UK>
     • Re: Stratified random sample using arrays (93 lines)
       From: Dale McLerran <stringplayer_2@YAHOO.COM>
     • Stratified random sample using arrays (23 lines)
       From: ben.powell@CLA.CO.UK

116. Substring Puzzle
     • Re: Substring Puzzle (99 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: Substring Puzzle (43 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: Substring Puzzle (90 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: Substring Puzzle (60 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: Substring Puzzle (58 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • Re: Substring Puzzle (37 lines)
       From: Dianne Rhodes <RHODESD1@WESTAT.COM>
     • Re: Substring Puzzle (72 lines)
       From: Laurel Copeland <Laurel.Copeland@MED.VA.GOV>
     • Re: Substring Puzzle (39 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • Re: Substring Puzzle (35 lines)
       From: Laurel Copeland <Laurel.Copeland@MED.VA.GOV>
     • Re: Substring Puzzle (57 lines)
       From: Dennis Diskin <diskin.dennis@KENDLE.COM>
     • Re: Substring Puzzle (36 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • Substring Puzzle (21 lines)
       From: aj <alg3210@YAHOO.COM>

117. Super Size Dataset from Cartesian Join
     • Re: Super Size Dataset from Cartesian Join (151 lines)
       From: pudding man <pudding_man@MAIL.COM>
     • Re: Super Size Dataset from Cartesian Join (120 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: Super Size Dataset from Cartesian Join (107 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: Super Size Dataset from Cartesian Join (169 lines)
       From: pudding man <pudding_man@MAIL.COM>
     • Re: Super Size Dataset from Cartesian Join (67 lines)
       From: News Reader <newsreader@MIDSOUTH.RR.COM>
     • Re: Super Size Dataset from Cartesian Join (170 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: Super Size Dataset from Cartesian Join (98 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: Super Size Dataset from Cartesian Join (87 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • Re: Super Size Dataset from Cartesian Join (112 lines)
       From: Michael S. Zdeb <msz03@HEALTH.STATE.NY.US>
     • Re: Super Size Dataset from Cartesian Join (75 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Super Size Dataset from Cartesian Join (59 lines)
       From: Dewen Hou <Dewen.Hou@BLOCKBUSTER.COM>

118. TIP: %IF Outside of Macro
     • Re: TIP: %IF Outside of Macro (125 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>

119. Temporary Character Array is Cutoff
     • Re: Temporary Character Array is Cutoff (38 lines)
       From: Busby, Phil <Phil.Busby@GMACERM.COM>
     • Re: Temporary Character Array is Cutoff (38 lines)
       From: Robin High <robinh@UNLSERVE.UNL.EDU>
     • Re: Temporary Character Array is Cutoff (40 lines)
       From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
     • Temporary Character Array is Cutoff (28 lines)
       From: Melanie J. <mbarish@PROGENICS.COM>

120. Test
     • Test (10 lines)
       From: Dewen Hou <Dewen.Hou@BLOCKBUSTER.COM>

121. Testing
     • Testing (14 lines)
       From: Dunn, Toby <tdunn@TEA.STATE.TX.US>

122. Time formatted field in Frame v8.2
     • Re: Time formatted field in Frame v8.2 (51 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: Time formatted field in Frame v8.2 (32 lines)
       From: Steve <sd44@EARTHLINK.NET>

123. Transpose Obs into Variables
     • Re: Transpose Obs into Variables (80 lines)
       From: Dubravko Dolic <dubro@DOLIC.DE>
     • Re: Transpose Obs into Variables (66 lines)
       From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
     • Transpose Obs into Variables (36 lines)
       From: Dubravko Dolic <dubro@DOLIC.DE>

124. Turnbull survival estimation - test of equality of strata?
     • Turnbull survival estimation - test of equality of strata? (23 lines)
       From: Jay Weedon <jweedon@EARTHLINK.NET>

125. UNSUBSCRIBE
     • UNSUBSCRIBE (18 lines)
       From: David FIckbohm <davefickbohm@YAHOO.COM>
     • Re: UNSUBSCRIBE (34 lines)
       From: F. J. Kelley <jkelley@UGA.EDU>
     • UNSUBSCRIBE (10 lines)
       From: Meadows, Jeremy <JMeadows@ALLDATA.NET>
     • UNSUBSCRIBE (11 lines)
       From: Ranjeet Gauni <ranjeetg@HOTMAIL.COM>
     • UNSUBSCRIBE (10 lines)
       From: Mike Wood <kamikaze@VERIZON.NET>

126. Unix commands in SAS
     • Re: Unix commands in SAS (33 lines)
       From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
     • Re: Unix commands in SAS (36 lines)
       From: SAS User <sas@SDAC.HARVARD.EDU>
     • Unix commands in SAS (21 lines)
       From: taran gujral <taran_jit@YAHOO.COM>

127. Urgent: 5000 Euro Reward (0.09929116184947906)
     • Urgent: 5000 Euro Reward (0.09929116184947906) (27 lines)
       From: 0.38964292501860376 <fasten@HRS.COM>

128. VERSION 9: The Big Picture?
     • Re: VERSION 9: The Big Picture? (57 lines)
       From: Peter Flom <flom@NDRI.ORG>
     • Re: VERSION 9: The Big Picture? (40 lines)
       From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK>
     • Re: VERSION 9: The Big Picture? (38 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: VERSION 9: The Big Picture? (166 lines)
       From: Shawn Edney <Edney.Shawn@EPAMAIL.EPA.GOV>
     • Re: VERSION 9: The Big Picture? (67 lines)
       From: Peter Flom <flom@NDRI.ORG>
     • Re: VERSION 9: The Big Picture? (52 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • Re: VERSION 9: The Big Picture? (37 lines)
       From: ben.powell@CLA.CO.UK
     • Re: VERSION 9: The Big Picture? (209 lines)
       From: Shawn Edney <Edney.Shawn@EPAMAIL.EPA.GOV>
     • Re: VERSION 9: The Big Picture? (151 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: VERSION 9: The Big Picture? (136 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>

129. WEEKEND VIAGRA
     • WEEKEND VIAGRA (19 lines)
       From: Domingo W. Rubio <drubio_wo@HOTMAIL.COM>

130. What are you gonna do with the new you?
     • What are you gonna do with the new you? (19 lines)
       From: Kendra Givens <kendra.givens_xw@EXCITE.COM>

131. What's wrong with this: street_n=addr1_1|" "||addr2||" "||addr3||" "||addr4||" "||addr5
     • Re: What's wrong with this: street_n=addr1_1|" "||addr2||" "||addr3||" "||addr4||" "||addr5 (94 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>

132. Why DATEPART function is not working
     • Re: Why DATEPART function is not working (108 lines)
       From: Venky Chakravarthy <venky.chakravarthy@PFIZER.COM>
     • Re: Why DATEPART function is not working (124 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: Why DATEPART function is not working (55 lines)
       From: Don Stanley <don_stanley@PARADISE.NET.NZ>
     • Re: Why DATEPART function is not working (128 lines)
       From: Nat Wooding <Nathaniel_Wooding@DOM.COM>
     • Re: Why DATEPART function is not working (89 lines)
       From: Anbu <aarumugam@STTHOMAS.EDU>

133. Will you be here?
     • Will you be here? (37 lines)
       From: Kelley Taylor <kelleytaylor_iw@CERIL.CL>

134. Writing hyperlinks to Excel with SAS
     • Re: Writing hyperlinks to Excel with SAS (118 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: Writing hyperlinks to Excel with SAS (21 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: Writing hyperlinks to Excel with SAS (20 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: Writing hyperlinks to Excel with SAS (10 lines)
       From: Arto Raiskio <arto-nospam@RAISKIO.COM>
     • Re: Writing hyperlinks to Excel with SAS (12 lines)
       From: Arto Raiskio <arto-nospam@RAISKIO.COM>
     • Re: Writing hyperlinks to Excel with SAS (101 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: Writing hyperlinks to Excel with SAS (53 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Writing hyperlinks to Excel with SAS (37 lines)
       From: Wall, Steven <steve.wall@PIONEER.COM>

135. Z2. Format
     • Re: Z2. Format (54 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: Z2. Format (27 lines)
       From: Kevin Roland Viel <kviel@EMORY.EDU>
     • Re: Z2. Format (52 lines)
       From: Dennis Diskin <diskin.dennis@KENDLE.COM>
     • Z2. Format (28 lines)
       From: Ross, Michael D <michael.ross@ASTRAZENECA.COM>

136. [SAS license assessment] Attention Toronto area SAS users
     • [SAS license assessment] Attention Toronto area SAS users (35 lines)
       From: Samuel <samuel@WATCHWISE.COM>

137. [v9] using hashes to merge data
     • Re: [v9] using hashes to merge data (20 lines)
       From: Arto Raiskio <arto-nospam@RAISKIO.COM>
     • [v9] using hashes to merge data (127 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

138. apologies
     • apologies (16 lines)
       From: Kerri Rivers <kerrir@PRB.ORG>

139. canonical analysis outside of proc rsreg
     • canonical analysis outside of proc rsreg (46 lines)
       From: Howard Rundle <h.rundle@UQ.EDU.AU>

140. changing default of character variable ; was Substring Puzzle
     • Re: changing default of character variable ; was Substring Puzzle (52 lines)
       From: Dianne Rhodes <RHODESD1@WESTAT.COM>

141. colapse several records into one
     • Re: colapse several records into one (85 lines)
       From: Nori Abakah <moree@BRAATPAQ.COM>
     • Re: colapse several records into one (77 lines)
       From: William Kossack <kossackw@NJC.ORG>
     • Re: colapse several records into one (62 lines)
       From: William Kossack <kossackw@NJC.ORG>
     • Re: colapse several records into one (52 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • Re: colapse several records into one (41 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • Re: colapse several records into one (60 lines)
       From: Roger Lustig <trovato@VERIZON.NET>
     • Re: colapse several records into one (42 lines)
       From: William Kossack <kossackw@NJC.ORG>
     • Re: colapse several records into one (42 lines)
       From: William Kossack <kossackw@NJC.ORG>
     • Re: colapse several records into one (37 lines)
       From: Roger Lustig <trovato@VERIZON.NET>
     • colapse several records into one (26 lines)
       From: William Kossack <kossackw@NJC.ORG>

142. compare records in two tables
     • Re: compare records in two tables (100 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: compare records in two tables (114 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: compare records in two tables (61 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • Re: compare records in two tables (100 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • Re: compare records in two tables (43 lines)
       From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
     • Re: compare records in two tables (49 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • compare records in two tables (23 lines)
       From: Dave Lytle <lytle_dave@HOTMAIL.COM>

143. compare records in two tables - clarification
     • Re: compare records in two tables - clarification (228 lines)
       From: pudding man <pudding_man@MAIL.COM>
     • Re: compare records in two tables - clarification (206 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: compare records in two tables - clarification (117 lines)
       From: Dave Lytle <lytle_dave@HOTMAIL.COM>

144. dataset conversion from v6 to v8
     • Re: dataset conversion from v6 to v8 (237 lines)
       From: Tim Braam <timothy.j.braam@CENSUS.GOV>
     • Re: dataset conversion from v6 to v8 (216 lines)
       From: Fuchs, Tom <Tom.Fuchs@LGEENERGY.COM>
     • Re: dataset conversion from v6 to v8 (188 lines)
       From: F. J. Kelley <jkelley@UGA.EDU>
     • Re: dataset conversion from v6 to v8 (157 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • Re: dataset conversion from v6 to v8 (9 lines)
       From: Frank Berger <frank.d.berger@DAL.FRB.ORG>
     • Re: dataset conversion from v6 to v8 (141 lines)
       From: Stephen Wan <swan@UGA.EDU>
     • Re: dataset conversion from v6 to v8 (83 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • Re: dataset conversion from v6 to v8 (89 lines)
       From: Andre Wielki <wielki@INED.FR>
     • Re: dataset conversion from v6 to v8 (53 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • dataset conversion from v6 to v8 (67 lines)
       From: Stephen Wan <swan@UGA.EDU>

145. detecting changes in data
     • Re: detecting changes in data (159 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

146. finding location in input statement
     • Re: finding location in input statement (36 lines)
       From: Robert Keith Elias <kelias@CLIC.NET>
     • Re: finding location in input statement (79 lines)
       From: Arthur Tabachneck <art297@NETSCAPE.NET>
     • Re: finding location in input statement (55 lines)
       From: Robert Keith Elias <kelias@CLIC.NET>
     • Re: finding location in input statement (63 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: finding location in input statement (37 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: finding location in input statement (56 lines)
       From: Jan Selchau-Hansen <jan@SELCHAU-HANSEN.INVALID>
     • finding location in input statement (49 lines)
       From: Robert Keith Elias <kelias@CLIC.NET>

147. gprobcnt
     • gprobcnt (65 lines)
       From: Carlos Tadeu <ctsdias@CARPA.CIAGRI.USP.BR>

148. help to find the logic
     • Re: help to find the logic (85 lines)
       From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
     • help to find the logic (33 lines)
       From: Vera <vzamniborsch@HOTMAIL.COM>

149. help with an error message
     • Re: help with an error message (47 lines)
       From: Don Stanley <don_stanley@PARADISE.NET.NZ>
     • help with an error message (41 lines)
       From: kevin <kevin20142000@YAHOO.COM>

150. how to use sql coalesce with time
     • Re: how to use sql coalesce with time (70 lines)
       From: Arto Raiskio <arto-nospam@RAISKIO.COM>
     • Re: how to use sql coalesce with time (23 lines)
       From: Arto Raiskio <arto-nospam@RAISKIO.COM>
     • Re: how to use sql coalesce with time (92 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: how to use sql coalesce with time (77 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • Re: how to use sql coalesce with time (71 lines)
       From: Arto Raiskio <arto-nospam@RAISKIO.COM>
     • Re: how to use sql coalesce with time (21 lines)
       From: Arto Raiskio <arto-nospam@RAISKIO.COM>
     • Re: how to use sql coalesce with time (33 lines)
       From: Arto Raiskio <arto-nospam@RAISKIO.COM>
     • Re: how to use sql coalesce with time (39 lines)
       From: Arto Raiskio <arto-nospam@RAISKIO.COM>
     • Re: how to use sql coalesce with time (131 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

151. ignore this ..this is just a test mail
     • Re: ignore this ..this is just a test mail (7 lines)
       From: Nageswara Rao Punnani <npunnani@MEMPHIS.EDU>

152. lag Return upto 12 time for unbalanced panel
     • Re: lag Return upto 12 time for unbalanced panel (181 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: lag Return upto 12 time for unbalanced panel (100 lines)
       From: Dale McLerran <stringplayer_2@YAHOO.COM>
     • lag Return upto 12 time for unbalanced panel (49 lines)
       From: sonia afroz <afroz_sonia@HOTMAIL.COM>

153. lag function
     • Re: lag function (68 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: lag function (119 lines)
       From: Robert Burbidge <RBurbidge@PHD.CO.UK>
     • Re: lag function (48 lines)
       From: Charles Patridge <charles_s_patridge@PRODIGY.NET>
     • lag function (67 lines)
       From: Chen, Jian <ozz6@CDC.GOV>

154. look for a simple way to define a macro variable
     • Re: look for a simple way to define a macro variable (24 lines)
       From: Yanal Ansouqa <ansouqa@SBCGLOBAL.NET>
     • look for a simple way to define a macro variable (36 lines)
       From: Ian Whitlock <iw1junk@COMCAST.NET>
     • Re: look for a simple way to define a macro variable (45 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: look for a simple way to define a macro variable (53 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: look for a simple way to define a macro variable (28 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • Re: look for a simple way to define a macro variable (37 lines)
       From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
     • look for a simple way to define a macro variable (16 lines)
       From: John Cui <cuij@CSHS.ORG>

155. macro help routines
     • macro help routines (77 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>

156. no growth then money back and u keep..
     • no growth then money back and u keep.. (18 lines)
       From: Sasha Marks <sashamarks_ei@AOL.COM>

157. odbc problem
     • Re: odbc problem (67 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • odbc problem (46 lines)
       From: William Kossack <kossackw@NJC.ORG>

158. output sum of vars to a file
     • Re: output sum of vars to a file (25 lines)
       From: Jonas Bilenas <Jonas.Bilenas@CHASE.COM>

159. pittfalls of data step loop
     • Re: pittfalls of data step loop (72 lines)
       From: Puhong Gao <pgao@ATT.NET>

160. proc appsrv et al
     • Re: proc appsrv et al (59 lines)
       From: Evert Carton <me@YOU.HE>
     • Re: proc appsrv et al (47 lines)
       From: Don Henderson <donaldjhenderson@HOTMAIL.COM>
     • proc appsrv et al (23 lines)
       From: Evert Carton <me@YOU.HE>

161. proc lifetest plots=(h) doesn`t work
     • Re: proc lifetest plots=(h) doesn`t work (25 lines)
       From: Jay Weedon <jweedon@EARTHLINK.NET>
     • proc lifetest plots=(h) doesn`t work (21 lines)
       From: Stefan Pohl <stefan.pohl@WISO.UNI-KOELN.DE>

162. proc regression macro ..
     • proc regression macro .. (33 lines)
       From: Nageswara Rao Punnani <npunnani@MEMPHIS.EDU>

163. proc sql question
     • Re: proc sql question (86 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: proc sql question (79 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

164. read the first 3 digit of the 4-digit data
     • Re: read the first 3 digit of the 4-digit data (73 lines)
       From: sportsfun <sportsfun77@HOTMAIL.COM>
     • Re: read the first 3 digit of the 4-digit data (39 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • read the first 3 digit of the 4-digit data (22 lines)
       From: sportsfun <sportsfun77@HOTMAIL.COM>
     • Re: read the first 3 digit of the 4-digit data (61 lines)
       From: Scott <usenet739_yahoo_com_au@CRONKITE.CC.UGA.EDU>

165. remove
     • Re: remove (30 lines)
       From: F. J. Kelley <jkelley@UGA.EDU>
     • remove (13 lines)
       From: Sandra Nutter <snutter@PROJECTS.SDSU.EDU>

166. reply fast
     • reply fast (51 lines)
       From: mary_daniels <mary_daniels@TELSTRA.COM>

167. report question
     • Re: report question (83 lines)
       From: Busby, Phil <Phil.Busby@GMACERM.COM>
     • report question (37 lines)
       From: rohitwmu <rohitwmu@INDIATIMES.COM>

168. tip macro Put_
     • Re: tip macro Put_ (103 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>
     • Re: tip macro Put_ (115 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: tip macro Put_ (253 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>
     • Re: tip macro Put_ (87 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: tip macro Put_ (195 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>
     • Re: tip macro Put_ (124 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • tip macro Put_ (87 lines)
       From: Ian Whitlock <iw1junk@COMCAST.NET>
     • tip macro Put_ (58 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>

169. truncated values in sashelp.vmacro
     • truncated values in sashelp.vmacro (44 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>

170. u might want to see this
     • u might want to see this (33 lines)
       From: Kellie McCann <kmcCannwe@ATOM.HU>

171. unsubscribe
     • unsubscribe (18 lines)
       From: David FIckbohm <davefickbohm@YAHOO.COM>

172. variable clarification
     • Re: variable clarification (59 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: variable clarification (35 lines)
       From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
     • variable clarification (24 lines)
       From: kevin <kevin20142000@YAHOO.COM>

173. what's the cmd for canceling submitted statements?
     • Re: what's the cmd for canceling submitted statements? (41 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: what's the cmd for canceling submitted statements? (35 lines)
       From: Andre Wielki <wielki@INED.FR>
     • what's the cmd for canceling submitted statements? (18 lines)
       From: Duck-Hye Yang <dyang@CHAPINHALL.ORG>

174. zero truncated poisson regression
     • Re: zero truncated poisson regression (65 lines)
       From: Dale McLerran <stringplayer_2@YAHOO.COM>
     • Re: zero truncated poisson regression (71 lines)
       From: Dale McLerran <stringplayer_2@YAHOO.COM>
     • zero truncated poisson regression (28 lines)
       From: Andrew Haywood <AndrewHa@SF.NSW.GOV.AU>