Table of contents:

• ;super Viagra 80% dis^count ` crrukqmzwb
• <No subject> (3 messages)
• Are You Still Looking.? ji pxjpqlbphdse
• Buy Valium/Diazepam - Overnight
• CALL EXECUTE and macro variables (7 messages)
• CATALOGs and GPLOT (3 messages)
• Calculating Differences by Group (3 messages)
• Calculating Differences by Group (SUMMARY)
• Can you make a SAS dataset READ ONLY? (4 messages)
• Clarification (3 messages)
• Comparing survival functions (2 messages)
• Copy Zip file in Lan to Unix (7 messages)
• Cross validation question (2 messages)
• DATE CONVERSION (2 messages)
• DON'T MISS THIS SPECIAL OFFER (2 messages)
• Difference in mean between 2 groups (5 messages)
• EARN $50,000 PLUS (it's easy and legal so at least read it!!)
• Enlarge your johnson
• Export t-values (2 messages)
• Export t-values II (2 messages)
• Export text file without variable names (5 messages)
• Export to Fixed Format ASCII - Extreme Newby Question (3 messages)
• Extended selection in Table Viewer v8
• FICO like scores (2 messages)
• Format Problem (2 messages)
• Formatting problem in alternate line in Proc Report (5 messages)
• GENESEE VALLEY (Rochester, NY area) SAS USER'S GROUP MEETING
• Generate artificial data for sample size simulation
• Get cheap via-gra
• Getting a copy of SAS to learn the language (5 messages)
• HELP NEW MACRO QUTOING QUESTION (3 messages)
• Have faith...
• Help (4 messages)
• Help with data.. (8 messages)
• How does SAS treat dates imported from Access Databases? (2 messages)
• INC0ME GENERAT0R
• INSERTing into EXCEL, PDF versus GIF (3 messages)
• Importing Excel file using URL engine ? (3 messages)
• Interesting? Input statement (7 messages)
• It's to good to pass up!
• JCL SPACE ALLOCATION ISSUES
• JOINT VENTURE. (3 messages)
• Kludge of the day (12 messages)
• Labels and Formats (3 messages)
• Long lasting viagra
• MACRO QUOTING QUESTION (5 messages)
• MAcro IN Operator
• MERGEing Excel cells via DDE (3 messages)
• MP Connect and SCL messaging services
• Macro Quoting Problem (11 messages)
• Macro calls in Proc SQL? (3 messages)
• Macro quoting and quoted string length (2 messages)
• March 11 MSUG Meeting
• Meta: comp.soft-sys.sas Usenet threading broken by SAS-L (4 messages)
• More efficient than via-gra
• Nested Macro Call Question (Macro Maven Alert!!) (6 messages)
• Neural Network Macro
• New message
• No more.
• ODS Graphics in Title
• ODS HTML
• ODS PDF and data _null_ (3 messages)
• ODS Topics at SAS User Group Meetings in SF Bay Area April 7 & 8
• ODS Topics at SAS User Group Meetings in SF BayArea /Corrected URL
• OT: Using ibm 122-type keyboards with terminal emulation soft ware going to a mainframe (2 messages)
• OT: Using ibm 122-type keyboards with terminal emulation software going to a mainframe (2 messages)
• OWl Cam Questions from all my Firends
• Oracle to SAS (3 messages)
• Outputting t-values
• Performance with long char variables
• Proc REPORT, how to fit many variables in continuous lines
• Proc Reg -- collecting test stats based on the heteroscadast iciy consistent covariance matrix
• Proc Reg -- collecting test stats based on the heteroscadasticiy
• Proc Reg -- collecting test stats based on the heteroscadasticiy consistent covariance matrix
• Proc Transpose On Missing ID Values (3 messages)
• Proc tabulate out=myfile question (2 messages)
• Q: Datafax to SAS (2 messages)
• Q: Generate artificial data for sample size simulation (2 messages)
• Querying LDAP for SMTP addresses
• Question about "row-level" processing for a dataset (4 messages)
• Question about how to edit Survival curve lables (3 messages)
• RE : Any experience ? (4 messages)
• RE : Viewtable
• RE : insert data into db
• RE : proc format question
• ROC curve outout (2 messages)
• Read Excel into SAS (4 messages)
• Read This....Please....
• Recently used File list from the file menu (5 messages)
• Ref: Help with data..
• Refinance at a low rate ' cjtqifb
• SAS Macro Seminar Available
• SAS Newsletter/Crossword??????
• SAS-L Digest - 4 Mar 2004 - Special issue (#2004-262) (Out of office)
• SAS-L@LISTSERV.UGA.EDU
• SASZIPAM (2 messages)
• SYMBOL and filling VALUE (2 messages)
• Somewhat OT: Restrictive employment contracts
• Statistics Q (2 messages)
• T00 G00D T00 MISS
• TIP: %IF Outside of Macro (2 messages)
• TIP: Change the statistic on a PROC REPORT total line
• TIP: RTF codes in PROC REPORT LINE statements (3 messages)
• Tabulate percentage question (newbie)
• Take control of your youth!
• Test Post
• Test post
• Thanks TTEST works well RE: Difference in mean between 2 groups
• The weekend viagra (2 messages)
• Time formatted field in Frame v8.2 (5 messages)
• Today is the first day of the rest of your life
• Trendline Equation - what is it?
• Trouble with a SAS "DO" Statement (21 x 21 x 21 x 21 loops) (6 messages)
• User asked for termination (5 messages)
• User asked for termination (Thanks) (2 messages)
• Validating Phone Numbers (10 messages)
• Variable creation (5 messages)
• Viewtable
• What's wrong with this:
• What's wrong with this: street_n=addr1_1|" "||addr2||" "||addr3||" "||addr4||" "||addr5 (6 messages)
• Why DATEPART function is not working (5 messages)
• Would An Extra Paycheck Next Month Help iz vzctfrz wi
• Writing to flat files on Unix
• X Axis in Proc Gplot (2 messages)
• [Q] Interpretation of dimensions in Correspondence Analysis
• census data on user friendly CD (3 messages)
• come check out this exclusive footage
• counting by-groups (4 messages)
• detecting changes in data (10 messages)
• employment
• graphics
• help
• help SAS/MS ACCESS, general database questions (4 messages)
• how its working? (Modified list input) (6 messages)
• how to use sql coalesce with time (4 messages)
• insert data into db
• macro parameter foolishness (6 messages)
• men growth enlarge ur manhood
• nlp query (2 messages)
• obtain external file date/time
• output sum of vars to a file (3 messages)
• pound sign causes macro problems in Version 9.1 (2 messages)
• proc discrim - nonparametric
• proc format question (4 messages)
• proc import truncating (2 messages)
• proc sql question (2 messages)
• raw data reading problem (4 messages)
• read about super H`G`H even better then normal H^G_H - srxdgkxardsscr
• reading part data (4 messages)
• removal from List (Out of office)
• remove "table of" generated by the freq procedure in ods html (2 messages)
• sas access - dbms
• select part of the text in the program editor and submit it (4 messages)
• syntax/reference for proc neural
• tab character as delimiter (5 messages)
• test post
• test post, please ignore
• trial interaction
• two-stage and fixed effects?
• unsubscribe
• using ODS to export to XLS problem...... (7 messages)
• what is the expansion for DSD? (11 messages)

1. ;super Viagra 80% dis^count ` crrukqmzwb
   • ;super Viagra 80% dis^count ` crrukqmzwb (35 lines)
     From: Jodi Franco <j_franco_on@UNI-MANNHEIM.DE>

2. <No subject>
   • <No subject> (9 lines)
     From: Matt Brown <matt_angelo_brown@USA.NET>
   • <No subject> (13 lines)
     From: David Kellerman <kellermandavid@YAHOO.COM>
   • <No subject> (78 lines)
     From: Ian Whitlock <iw1junk@COMCAST.NET>

3. Are You Still Looking.? ji pxjpqlbphdse
   • Are You Still Looking.? ji pxjpqlbphdse (80 lines)
     From: Pete Messer <iantibus@FIREMAIL.DE>

4. Buy Valium/Diazepam - Overnight
   • Buy Valium/Diazepam - Overnight (19 lines)
     From: Gerardo K. Morrow <gerardo_morrowge@AZCOGEN.DEMON.CO.UK>

5. CALL EXECUTE and macro variables
   • CALL EXECUTE and macro variables (30 lines)
     From: Kevin Roland Viel <kviel@EMORY.EDU>
   • Re: CALL EXECUTE and macro variables (43 lines)
     From: Don Stanley <don_stanley@PARADISE.NET.NZ>
   • Re: CALL EXECUTE and macro variables (40 lines)
     From: Lou <lpogodajr292185@COMCAST.NET>
   • Re: CALL EXECUTE and macro variables (94 lines)
     From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
   • Re: CALL EXECUTE and macro variables (65 lines)
     From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
   • Re: CALL EXECUTE and macro variables (196 lines)
     From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>
   • Re: CALL EXECUTE and macro variables (27 lines)
     From: Kevin Roland Viel <kviel@EMORY.EDU>

6. CATALOGs and GPLOT
   • CATALOGs and GPLOT (38 lines)
     From: Kevin Roland Viel <kviel@EMORY.EDU>
   • Re: CATALOGs and GPLOT (56 lines)
     From: Don Henderson <donaldjhenderson@HOTMAIL.COM>
   • Re: CATALOGs and GPLOT (26 lines)
     From: Kevin Roland Viel <kviel@EMORY.EDU>

7. Calculating Differences by Group
   • Calculating Differences by Group (71 lines)
     From: Robert Burbidge <RBurbidge@PHD.CO.UK>
   • Re: Calculating Differences by Group (91 lines)
     From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
   • Re: Calculating Differences by Group (31 lines)
     From: m n <iced_phoenix@YAHOO.COM>

8. Calculating Differences by Group (SUMMARY)
   • Re: Calculating Differences by Group (SUMMARY) (104 lines)
     From: Robert Burbidge <RBurbidge@PHD.CO.UK>

9. Can you make a SAS dataset READ ONLY?
   • Can you make a SAS dataset READ ONLY? (13 lines)
     From: Conrad, Douglas <Douglas.Conrad@FMR.COM>
   • Re: Can you make a SAS dataset READ ONLY? (24 lines)
     From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
   • Re: Can you make a SAS dataset READ ONLY? (45 lines)
     From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
   • Re: Can you make a SAS dataset READ ONLY? (70 lines)
     From: Conrad, Douglas <Douglas.Conrad@FMR.COM>

10. Clarification
    • Clarification (19 lines)
      From: Ellen Rains <erains@NERI.ORG>
    • Re: Clarification (50 lines)
      From: Dennis Diskin <diskin.dennis@KENDLE.COM>
    • Re: Clarification (30 lines)
      From: Gina Nicolosi <ginanicolosi@HOTMAIL.COM>

11. Comparing survival functions
    • Comparing survival functions (25 lines)
      From: Mats Andersson <loglikelihood@HOTMAIL.COM>
    • Re: Comparing survival functions (51 lines)
      From: DePuy, Venita <depuy001@DCRI.DUKE.EDU>

12. Copy Zip file in Lan to Unix
    • Copy Zip file in Lan to Unix (27 lines)
      From: Chandu <mailrajuv@YAHOO.COM>
    • Re: Copy Zip file in Lan to Unix (60 lines)
      From: Karsten M. Self <kmself@IX.NETCOM.COM>
    • Re: Copy Zip file in Lan to Unix (66 lines)
      From: Chandu <mailrajuv@YAHOO.COM>
    • Re: Copy Zip file in Lan to Unix (85 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
    • Re: Copy Zip file in Lan to Unix (38 lines)
      From: Karsten M. Self <kmself@IX.NETCOM.COM>
    • Re: Copy Zip file in Lan to Unix (90 lines)
      From: Karsten M. Self <kmself@IX.NETCOM.COM>
    • Re: Copy Zip file in Lan to Unix (36 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

13. Cross validation question
    • Cross validation question (38 lines)
      From: Peter Flom <flom@NDRI.ORG>
    • Re: Cross validation question (134 lines)
      From: bogdan romocea <br44092@GAWAB.COM>

14. DATE CONVERSION
    • DATE CONVERSION (19 lines)
      From: Tonkovich, Mike <Mike.Tonkovich@DNR.STATE.OH.US>
    • Re: DATE CONVERSION (33 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

15. DON'T MISS THIS SPECIAL OFFER
    • DON'T MISS THIS SPECIAL OFFER (106 lines)
      From: Jim <jolly.pirate@TISCALI.CO.UK>
    • Re: DON'T MISS THIS SPECIAL OFFER (107 lines)
      From: Gary Ross <gary_ross@MGIC.COM>

16. Difference in mean between 2 groups
    • Difference in mean between 2 groups (49 lines)
      From: Elmaache, Hamani <Hamani.Elmaache@CCRA-ADRC.GC.CA>
    • Re: Difference in mean between 2 groups (80 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
    • Re: Difference in mean between 2 groups (84 lines)
      From: Peter Flom <flom@NDRI.ORG>
    • Re: Difference in mean between 2 groups (55 lines)
      From: Roger Lustig <trovato@VERIZON.NET>
    • Re: Difference in mean between 2 groups (111 lines)
      From: bogdan romocea <br44092@GAWAB.COM>

17. EARN $50,000 PLUS (it's easy and legal so at least read it!!)
    • EARN $50,000 PLUS (it's easy and legal so at least read it!!) (203 lines)
      From: Blork <blork@HOTMAIL.COM>

18. Enlarge your johnson
    • Enlarge your johnson (18 lines)
      From: Guadalupe Lee <guadalupe.lee_zp@A-LINE.DEMON.CO.UK>

19. Export t-values
    • Export t-values (53 lines)
      From: Christine Wieck <wieck@AGP.UNI-BONN.DE>
    • Re: Export t-values (69 lines)
      From: DePuy, Venita <depuy001@DCRI.DUKE.EDU>

20. Export t-values II
    • Export t-values II (81 lines)
      From: Christine Wieck <wieck@AGP.UNI-BONN.DE>
    • Re: Export t-values II (11 lines)
      From: Gina Nicolosi <ginanicolosi@HOTMAIL.COM>

21. Export text file without variable names
    • Export text file without variable names (16 lines)
      From: Pat Moore <pat.moore@UAA.ALASKA.EDU>
    • Re: Export text file without variable names (49 lines)
      From: Bruce Johnson <bjohnson@SOLUCIENT.COM>
    • Re: Export text file without variable names (20 lines)
      From: Roy@HOME.NOT
    • Re: Export text file without variable names (46 lines)
      From: Nitin Chandak <nitin.chandak@GLOBALCASE.NET>
    • Re: Export text file without variable names (44 lines)
      From: Nat Wooding <Nathaniel_Wooding@DOM.COM>

22. Export to Fixed Format ASCII - Extreme Newby Question
    • Re: Export to Fixed Format ASCII - Extreme Newby Question (42 lines)
      From: Roy@HOME.NOT
    • Re: Export to Fixed Format ASCII - Extreme Newby Question (53 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Export to Fixed Format ASCII - Extreme Newby Question (28 lines)
      From: Roy@HOME.NOT

23. Extended selection in Table Viewer v8
    • Re: Extended selection in Table Viewer v8 (24 lines)
      From: Alex Jahnke <ajahnke@DADEBEHRING.COM>

24. FICO like scores
    • FICO like scores (14 lines)
      From: Hari Nair <hjnair@YAHOO.COM>
    • Re: FICO like scores (28 lines)
      From: Roger Lustig <trovato@VERIZON.NET>

25. Format Problem
    • Format Problem (77 lines)
      From: sreevatsan <sreevat.s@GLOBALCASE.NET>
    • Re: Format Problem (110 lines)
      From: Don Stanley <don_stanley@PARADISE.NET.NZ>

26. Formatting problem in alternate line in Proc Report
    • Formatting problem in alternate line in Proc Report (112 lines)
      From: Anbu Arasu <aarumugam@STTHOMAS.EDU>
    • Re: Formatting problem in alternate line in Proc Report (149 lines)
      From: Don Stanley <don_stanley@PARADISE.NET.NZ>
    • Re: Formatting problem in alternate line in Proc Report (158 lines)
      From: Anbu Arasu <aarumugam@STTHOMAS.EDU>
    • Re: Formatting problem in alternate line in Proc Report (181 lines)
      From: Andre Wielki <wielki@INED.FR>
    • Re: Formatting problem in alternate line in Proc Report (178 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>

27. GENESEE VALLEY (Rochester, NY area) SAS USER'S GROUP MEETING
    • GENESEE VALLEY (Rochester, NY area) SAS USER'S GROUP MEETING (62 lines)
      From: Paige Miller <paige.miller@KODAK.COM>

28. Generate artificial data for sample size simulation
    • Re: Generate artificial data for sample size simulation (58 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>

29. Get cheap via-gra
    • Get cheap via-gra (23 lines)
      From: Veronica Sherman <v_shermanec@ORIGINET.COM.BR>

30. Getting a copy of SAS to learn the language
    • Getting a copy of SAS to learn the language (39 lines)
      From: Robert Keith Elias <kelias@CLIC.NET>
    • Re: Getting a copy of SAS to learn the language (46 lines)
      From: Lou <lpogodajr292185@COMCAST.NET>
    • Re: Getting a copy of SAS to learn the language (79 lines)
      From: Robert Keith Elias <kelias@CLIC.NET>
    • Re: Getting a copy of SAS to learn the language (115 lines)
      From: Don Henderson <donaldjhenderson@HOTMAIL.COM>
    • Re: Getting a copy of SAS to learn the language (170 lines)
      From: John F. Regus <jfregus@IX.NETCOM.COM>

31. HELP NEW MACRO QUTOING QUESTION
    • HELP NEW MACRO QUTOING QUESTION (26 lines)
      From: sas programmer <sasprogrammer@HOTMAIL.COM>
    • Re: HELP NEW MACRO QUTOING QUESTION (45 lines)
      From: Dennis Diskin <diskin.dennis@KENDLE.COM>
    • Re: HELP NEW MACRO QUTOING QUESTION (14 lines)
      From: sas programmer <sasprogrammer@HOTMAIL.COM>

32. Have faith...
    • Have faith... (18 lines)
      From: Lillie Mullins <lilliemullins_yz@ASE.MD>

33. Help
    • Help (15 lines)
      From: Ellen Rains <erains@NERI.ORG>
    • Re: Help (41 lines)
      From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
    • Re: Help (26 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Help (42 lines)
      From: Bruce Johnson <bjohnson@SOLUCIENT.COM>

34. Help with data..
    • Help with data.. (53 lines)
      From: Nagakumar Sridhar <nsridhar@ATHEROGENICS.COM>
    • Re: Help with data.. (97 lines)
      From: Terjeson, Mark <TERJEM@DSHS.WA.GOV>
    • Re: Help with data.. (60 lines)
      From: DePuy, Venita <depuy001@DCRI.DUKE.EDU>
    • Re: Help with data.. (112 lines)
      From: Nagakumar Sridhar <nsridhar@ATHEROGENICS.COM>
    • Re: Help with data.. (80 lines)
      From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
    • Re: Help with data.. (31 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: Help with data.. (39 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: Help with data.. (62 lines)
      From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>

35. How does SAS treat dates imported from Access Databases?
    • How does SAS treat dates imported from Access Databases? (27 lines)
      From: Christopher Amherst <camherst@MISER.UMASS.EDU>
    • Re: How does SAS treat dates imported from Access Databases? (42 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>

36. INC0ME GENERAT0R
    • INC0ME GENERAT0R (106 lines)
      From: John Doe <john@DOE.COM>

37. INSERTing into EXCEL, PDF versus GIF
    • INSERTing into EXCEL, PDF versus GIF (25 lines)
      From: Kevin Roland Viel <kviel@EMORY.EDU>
    • Re: INSERTing into EXCEL, PDF versus GIF (33 lines)
      From: Kevin Roland Viel <kviel@EMORY.EDU>
    • Re: INSERTing into EXCEL, PDF versus GIF (58 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

38. Importing Excel file using URL engine ?
    • Re: Importing Excel file using URL engine ? (255 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Importing Excel file using URL engine ? (187 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
    • Re: Importing Excel file using URL engine ? (53 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

39. Interesting? Input statement
    • Interesting? Input statement (39 lines)
      From: PD <sophe88@YAHOO.COM>
    • Re: Interesting? Input statement (76 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Interesting? Input statement (55 lines)
      From: Don Stanley <don_stanley@PARADISE.NET.NZ>
    • Re: Interesting? Input statement (43 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Interesting? Input statement (60 lines)
      From: PD <sophe88@YAHOO.COM>
    • Re: Interesting? Input statement (65 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Interesting? Input statement (62 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

40. It's to good to pass up!
    • It's to good to pass up! (18 lines)
      From: Vicki Lehman <vickilehmanlk@BROADTECH.CO.NZ>

41. JCL SPACE ALLOCATION ISSUES
    • Re: JCL SPACE ALLOCATION ISSUES (149 lines)
      From: Toby Dunn <tdunn@OAKHILLTECH.COM>

42. JOINT VENTURE.
    • JOINT VENTURE. (79 lines)
      From: Adeshola Adeyemo <adadeyemo_attn@MYFAMILYMAIL.BIZ>
    • Re: JOINT VENTURE. (12 lines)
      From: Fletcher, Kevin <KEVIN_FLETCHER@CONSECO.COM>
    • Re: JOINT VENTURE. (101 lines)
      From: Vincent Granville <paris63@PACBEL.NET>

43. Kludge of the day
    • Kludge of the day (29 lines)
      From: Nat Wooding <Nathaniel_Wooding@DOM.COM>
    • Re: Kludge of the day (40 lines)
      From: Don Stanley <don_stanley@PARADISE.NET.NZ>
    • Re: Kludge of the day (68 lines)
      From: Lex Jansen <spam@LEXJANSEN.COM>
    • Re: Kludge of the day (60 lines)
      From: Randy Herbison <RandyHerbison@WESTAT.COM>
    • Re: Kludge of the day (62 lines)
      From: William W. Viergever <wwvierg@ATTGLOBAL.NET>
    • Re: Kludge of the day (81 lines)
      From: Lex Jansen <spam@LEXJANSEN.COM>
    • Re: Kludge of the day (83 lines)
      From: Nat Wooding <Nathaniel_Wooding@DOM.COM>
    • Re: Kludge of the day (37 lines)
      From: Paige Miller <paige.miller@KODAK.COM>
    • Re: Kludge of the day (135 lines)
      From: Atkinson, David <datkinso@NRCAN.GC.CA>
    • Re: Kludge of the day (172 lines)
      From: Nat Wooding <Nathaniel_Wooding@DOM.COM>
    • Re: Kludge of the day (118 lines)
      From: Boylan, David <DBoylan@HRBLOCK.COM>
    • Re: Kludge of the day (42 lines)
      From: Farrer, Andrew C <Andrew.Farrer@CIBC.COM>

44. Labels and Formats
    • Labels and Formats (21 lines)
      From: Steve Zelasky <sas_learner2000@YAHOO.COM>
    • Re: Labels and Formats (45 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
    • Re: Labels and Formats (57 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>

45. Long lasting viagra
    • Long lasting viagra (19 lines)
      From: Dewey Shafer <dewey_shafer_wc@AXEL.CO.JP>

46. MACRO QUOTING QUESTION
    • MACRO QUOTING QUESTION (24 lines)
      From: sas programmer <sasprogrammer@HOTMAIL.COM>
    • Re: MACRO QUOTING QUESTION (30 lines)
      From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
    • Re: MACRO QUOTING QUESTION (73 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
    • Re: MACRO QUOTING QUESTION (40 lines)
      From: kanthan <airaha_m@REDIFFMAIL.COM>
    • Re: MACRO QUOTING QUESTION (85 lines)
      From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>

47. MAcro IN Operator
    • MAcro IN Operator (32 lines)
      From: Don Stanley <don_stanley@PARADISE.NET.NZ>

48. MERGEing Excel cells via DDE
    • MERGEing Excel cells via DDE (27 lines)
      From: Kevin Roland Viel <kviel@EMORY.EDU>
    • Re: MERGEing Excel cells via DDE (37 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: MERGEing Excel cells via DDE (74 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>

49. MP Connect and SCL messaging services
    • Re: MP Connect and SCL messaging services (25 lines)
      From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>

50. Macro Quoting Problem
    • Macro Quoting Problem (29 lines)
      From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
    • Re: Macro Quoting Problem (46 lines)
      From: Farrer, Andrew C <Andrew.Farrer@CIBC.COM>
    • Re: Macro Quoting Problem (52 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Macro Quoting Problem (44 lines)
      From: Arthur Tabachneck <art297@NETSCAPE.NET>
    • Re: Macro Quoting Problem (81 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
    • Re: Macro Quoting Problem (170 lines)
      From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
    • Re: Macro Quoting Problem (214 lines)
      From: Don Henderson <donaldjhenderson@HOTMAIL.COM>
    • Re: Macro Quoting Problem (257 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
    • Re: Macro Quoting Problem (258 lines)
      From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
    • Re: Macro Quoting Problem (304 lines)
      From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
    • Re: Macro Quoting Problem (288 lines)
      From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>

51. Macro calls in Proc SQL?
    • Macro calls in Proc SQL? (24 lines)
      From: Dewen Hou <Dewen.Hou@BLOCKBUSTER.COM>
    • Re: Macro calls in Proc SQL? (34 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Macro calls in Proc SQL? (70 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

52. Macro quoting and quoted string length
    • Macro quoting and quoted string length (40 lines)
      From: Bruce Bradbury <BruceBrad@INAME.COM>
    • Re: Macro quoting and quoted string length (58 lines)
      From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>

53. March 11 MSUG Meeting
    • March 11 MSUG Meeting (24 lines)
      From: Nancy Brucken <brucken@PROVIDE.NET>

54. Meta: comp.soft-sys.sas Usenet threading broken by SAS-L
    • Meta: comp.soft-sys.sas Usenet threading broken by SAS-L (43 lines)
      From: Karsten M. Self <kmself@IX.NETCOM.COM>
    • Re: Meta: comp.soft-sys.sas Usenet threading broken by SAS-L (68 lines)
      From: F. J. Kelley <jkelley@UGA.EDU>
    • Re: Meta: comp.soft-sys.sas Usenet threading broken by SAS-L (39 lines)
      From: Karsten M. Self <kmself@IX.NETCOM.COM>
    • Re: Meta: comp.soft-sys.sas Usenet threading broken by SAS-L (107 lines)
      From: Karsten M. Self <kmself@IX.NETCOM.COM>

55. More efficient than via-gra
    • More efficient than via-gra (21 lines)
      From: Harvey Lackey <lackeypd@GIJK.DE>

56. Nested Macro Call Question (Macro Maven Alert!!)
    • Nested Macro Call Question (Macro Maven Alert!!) (34 lines)
      From: Conrad, Douglas <Douglas.Conrad@FMR.COM>
    • Re: Nested Macro Call Question (Macro Maven Alert!!) (48 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Nested Macro Call Question (Macro Maven Alert!!) (69 lines)
      From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
    • Re: Nested Macro Call Question (Macro Maven Alert!!) (35 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
    • Re: Nested Macro Call Question (Macro Maven Alert!!) (43 lines)
      From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
    • Nested Macro Call Question (Macro Maven Alert!!) (70 lines)
      From: Ian Whitlock <iw1junk@COMCAST.NET>

57. Neural Network Macro
    • Re: Neural Network Macro (60 lines)
      From: Atkinson, David <datkinso@NRCAN.GC.CA>

58. New message
    • New message (102 lines)
      From: John Doe <john@DOE.COM>

59. No more.
    • No more. (36 lines)
      From: Chester Palacios <chesterpalacios_xk@CHALLENGER.CA>

60. ODS Graphics in Title
    • ODS Graphics in Title (38 lines)
      From: David M. Kellerman <kellermandavid@YAHOO.COM>

61. ODS HTML
    • Re: ODS HTML (33 lines)
      From: Yanal Ansouqa <ansouqa@SBCGLOBAL.NET>

62. ODS PDF and data _null_
    • ODS PDF and data _null_ (20 lines)
      From: Mike Swift <mswift@AESSUCCESS.ORG>
    • Re: ODS PDF and data _null_ (89 lines)
      From: Delaney, Kevin P. <khd8@CDC.GOV>
    • Re: ODS PDF and data _null_ (51 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>

63. ODS Topics at SAS User Group Meetings in SF Bay Area April 7 & 8
    • ODS Topics at SAS User Group Meetings in SF Bay Area April 7 & 8 (46 lines)
      From: Andrew H. Karp <sfbay0001@AOL.COMNOPE>

64. ODS Topics at SAS User Group Meetings in SF BayArea /Corrected URL
    • ODS Topics at SAS User Group Meetings in SF BayArea /Corrected URL (23 lines)
      From: Andrew H. Karp <sfbay0001@AOL.COMNOPE>

65. OT: Using ibm 122-type keyboards with terminal emulation soft ware going to a mainframe
    • Re: OT: Using ibm 122-type keyboards with terminal emulation soft ware going to a mainframe (72 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
    • Re: OT: Using ibm 122-type keyboards with terminal emulation soft ware going to a mainframe (38 lines)
      From: Nat Wooding <Nathaniel_Wooding@DOM.COM>

66. OT: Using ibm 122-type keyboards with terminal emulation software going to a mainframe
    • OT: Using ibm 122-type keyboards with terminal emulation software going to a mainframe (22 lines)
      From: Nat Wooding <Nathaniel_Wooding@DOM.COM>
    • Re: OT: Using ibm 122-type keyboards with terminal emulation software going to a mainframe (38 lines)
      From: Charles Harbour <harbourcharles@JOHNDEERE.COM>

67. OWl Cam Questions from all my Firends
    • OWl Cam Questions from all my Firends (19 lines)
      From: Roy@HOME.NOT

68. Oracle to SAS
    • Oracle to SAS (17 lines)
      From: Steve Zelasky <sas_learner2000@YAHOO.COM>
    • Re: Oracle to SAS (59 lines)
      From: Dennis Diskin <diskin.dennis@KENDLE.COM>
    • Re: Oracle to SAS (44 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

69. Outputting t-values
    • Outputting t-values (24 lines)
      From: Krishna R. Kumar <kkumar@GWU.EDU>

70. Performance with long char variables
    • Re: Performance with long char variables (67 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

71. Proc REPORT, how to fit many variables in continuous lines
    • Re: Proc REPORT, how to fit many variables in continuous lines (47 lines)
      From: Liyan Liu <liyanliu888@YAHOO.COM>

72. Proc Reg -- collecting test stats based on the heteroscadast iciy consistent covariance matrix
    • Re: Proc Reg -- collecting test stats based on the heteroscadast iciy consistent covariance matrix (51 lines)
      From: DePuy, Venita <depuy001@DCRI.DUKE.EDU>

73. Proc Reg -- collecting test stats based on the heteroscadasticiy
    • Re: Proc Reg -- collecting test stats based on the heteroscadasticiy (39 lines)
      From: Paige Miller <paige.miller@KODAK.COM>

74. Proc Reg -- collecting test stats based on the heteroscadasticiy consistent covariance matrix
    • Proc Reg -- collecting test stats based on the heteroscadasticiy consistent covariance matrix (26 lines)
      From: Krishna R. Kumar <kkumar@GWU.EDU>

75. Proc Transpose On Missing ID Values
    • Proc Transpose On Missing ID Values (22 lines)
      From: LarsenMTL <larsmtl@YAHOO.COM>
    • Re: Proc Transpose On Missing ID Values (46 lines)
      From: Don Stanley <don_stanley@PARADISE.NET.NZ>
    • Re: Proc Transpose On Missing ID Values (70 lines)
      From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>

76. Proc tabulate out=myfile question
    • Proc tabulate out=myfile question (13 lines)
      From: knvsol <knvsol@COMCAST.NET>
    • Re: Proc tabulate out=myfile question (53 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>

77. Q: Datafax to SAS
    • Q: Datafax to SAS (29 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
    • Re: Q: Datafax to SAS (52 lines)
      From: lpogoda <lpogoda@HOTMAIL.COM>

78. Q: Generate artificial data for sample size simulation
    • Q: Generate artificial data for sample size simulation (29 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
    • Re: Q: Generate artificial data for sample size simulation (59 lines)
      From: Dennis Diskin <diskin.dennis@KENDLE.COM>

79. Querying LDAP for SMTP addresses
    • Querying LDAP for SMTP addresses (20 lines)
      From: Farrer, Andrew C <Andrew.Farrer@CIBC.COM>

80. Question about "row-level" processing for a dataset
    • Question about "row-level" processing for a dataset (83 lines)
      From: Sober Hi <soberhi@YAHOO.COM>
    • Re: Question about "row-level" processing for a dataset (119 lines)
      From: Dennis Diskin <diskin.dennis@KENDLE.COM>
    • Re: Question about "row-level" processing for a dataset (108 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Question about "row-level" processing for a dataset (18 lines)
      From: Sober Hi <soberhi@YAHOO.COM>

81. Question about how to edit Survival curve lables
    • Question about how to edit Survival curve lables (22 lines)
      From: jn mao <jn_mao@YAHOO.COM>
    • Re: Question about how to edit Survival curve lables (44 lines)
      From: DePuy, Venita <depuy001@DCRI.DUKE.EDU>
    • Re: Question about how to edit Survival curve lables (20 lines)
      From: jn mao <jn_mao@YAHOO.COM>

82. RE : Any experience ?
    • RE : Any experience ? (110 lines)
      From: Tanya Kolosova <tanya@WATCHWISE.COM>
    • Re: RE : Any experience ? (63 lines)
      From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
    • Re: RE : Any experience ? (176 lines)
      From: Phil Rack <philrack@MINEQUEST.COM>
    • Re: RE : Any experience ? (42 lines)
      From: Tanya Kolosova <tanya@WATCHWISE.COM>

83. RE : Viewtable
    • RE : Viewtable (117 lines)
      From: Datametric <datametric@CLUB-INTERNET.FR>

84. RE : insert data into db
    • RE : insert data into db (77 lines)
      From: Datametric <datametric@CLUB-INTERNET.FR>

85. RE : proc format question
    • RE : proc format question (50 lines)
      From: Datametric <datametric@CLUB-INTERNET.FR>

86. ROC curve outout
    • ROC curve outout (104 lines)
      From: Richard Goy <rgoy@UOGUELPH.CA>
    • Re: ROC curve outout (143 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

87. Read Excel into SAS
    • Read Excel into SAS (19 lines)
      From: S. S. <sassysaser@YAHOO.COM>
    • Re: Read Excel into SAS (33 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
    • Re: Read Excel into SAS (66 lines)
      From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>
    • Re: Read Excel into SAS (35 lines)
      From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL>

88. Read This....Please....
    • Read This....Please.... (191 lines)
      From: Bob <BobLoblaw@ROGERS.COM>

89. Recently used File list from the file menu
    • Recently used File list from the file menu (24 lines)
      From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM>
    • Re: Recently used File list from the file menu (37 lines)
      From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
    • Re: Recently used File list from the file menu (44 lines)
      From: Lex Jansen <spam@LEXJANSEN.COM>
    • Re: Recently used File list from the file menu (38 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
    • Re: Recently used File list from the file menu (70 lines)
      From: Venky Chakravarthy <venky.chakravarthy@PFIZER.COM>

90. Ref: Help with data..
    • Ref: Help with data.. (27 lines)
      From: Nagakumar Sridhar <nsridhar@ATHEROGENICS.COM>

91. Refinance at a low rate ' cjtqifb
    • Refinance at a low rate ' cjtqifb (28 lines)
      From: Russell Cody <rcodycj@DANSKEHOTELLER.DK>

92. SAS Macro Seminar Available
    • SAS Macro Seminar Available (23 lines)
      From: Michael Mitchell <mnm@UCLA.EDU>

93. SAS Newsletter/Crossword??????
    • SAS Newsletter/Crossword?????? (15 lines)
      From: SAS Plumber <sasplumber@HOTMAIL.COM>

94. SAS-L Digest - 4 Mar 2004 - Special issue (#2004-262) (Out of office)
    • Re: SAS-L Digest - 4 Mar 2004 - Special issue (#2004-262) (Out of office) (14 lines)
      From: Jennifer R Popovic <PopovicJ@GAO.GOV>

95. SAS-L@LISTSERV.UGA.EDU
    • SAS-L@LISTSERV.UGA.EDU (134 lines)
      From: bogdan romocea <br44092@GAWAB.COM>

96. SASZIPAM
    • SASZIPAM (16 lines)
      From: L. Bertolini <bertolini.1@OSU.EDU>
    • Re: SASZIPAM (31 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>

97. SYMBOL and filling VALUE
    • SYMBOL and filling VALUE (23 lines)
      From: Kevin Roland Viel <kviel@EMORY.EDU>
    • Re: SYMBOL and filling VALUE (44 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

98. Somewhat OT: Restrictive employment contracts
    • Re: Somewhat OT: Restrictive employment contracts (27 lines)
      From: Philip Gallagher <PGall9898@AOL.COM>

99. Statistics Q
    • Statistics Q (19 lines)
      From: Sun Bow <sunbow4u@HOTMAIL.COM>
    • Re: Statistics Q (21 lines)
      From: Gina Nicolosi <ginanicolosi@HOTMAIL.COM>

100. T00 G00D T00 MISS
     • T00 G00D T00 MISS (107 lines)
       From: John Doe <john@DOE.COM>

101. TIP: %IF Outside of Macro
     • TIP: %IF Outside of Macro (84 lines)
       From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
     • Re: TIP: %IF Outside of Macro (107 lines)
       From: Roger DeAngelis <xlr82sas@AOL.COM>

102. TIP: Change the statistic on a PROC REPORT total line
     • TIP: Change the statistic on a PROC REPORT total line (104 lines)
       From: Don Stanley <don_stanley@PARADISE.NET.NZ>

103. TIP: RTF codes in PROC REPORT LINE statements
     • TIP: RTF codes in PROC REPORT LINE statements (29 lines)
       From: Don Stanley <don_stanley@PARADISE.NET.NZ>
     • Re: TIP: RTF codes in PROC REPORT LINE statements (90 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>
     • Re: TIP: RTF codes in PROC REPORT LINE statements (109 lines)
       From: Don Stanley <don_stanley@PARADISE.NET.NZ>

104. Tabulate percentage question (newbie)
     • Tabulate percentage question (newbie) (31 lines)
       From: knvsol <knvsol@COMCAST.NET>

105. Take control of your youth!
     • Take control of your youth! (19 lines)
       From: Angela McCarty <a_mcCartyyl@HOTMAIL.COM>

106. Test Post
     • Test Post (9 lines)
       From: Randy Herbison <RandyHerbison@WESTAT.COM>

107. Test post
     • Test post (23 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

108. Thanks TTEST works well RE: Difference in mean between 2 groups
     • Thanks TTEST works well RE: Difference in mean between 2 groups (68 lines)
       From: Elmaache, Hamani <Hamani.Elmaache@CCRA-ADRC.GC.CA>

109. The weekend viagra
     • The weekend viagra (18 lines)
       From: Kari Tate <tatepg@HOTMAIL.COM>
     • The weekend viagra (19 lines)
       From: Anastasia Gilbert <anastasiagilbertwz@ARTURIPR.CO.UK>

110. Time formatted field in Frame v8.2
     • Time formatted field in Frame v8.2 (29 lines)
       From: Steve <sd44@EARTHLINK.NET>
     • Re: Time formatted field in Frame v8.2 (37 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: Time formatted field in Frame v8.2 (38 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • Re: Time formatted field in Frame v8.2 (44 lines)
       From: Steve <sd44@EARTHLINK.NET>
     • Re: Time formatted field in Frame v8.2 (25 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

111. Today is the first day of the rest of your life
     • Today is the first day of the rest of your life (19 lines)
       From: Staci Ryan <s_ryanqf@CALWIN.DK>

112. Trendline Equation - what is it?
     • Re: Trendline Equation - what is it? (137 lines)
       From: Peter Flom <flom@NDRI.ORG>

113. Trouble with a SAS "DO" Statement (21 x 21 x 21 x 21 loops)
     • Trouble with a SAS "DO" Statement (21 x 21 x 21 x 21 loops) (51 lines)
       From: Dan Yoo <byoo111@YAHOO.COM>
     • Re: Trouble with a SAS "DO" Statement (21 x 21 x 21 x 21 loops) (73 lines)
       From: DePuy, Venita <depuy001@DCRI.DUKE.EDU>
     • Re: Trouble with a SAS "DO" Statement (21 x 21 x 21 x 21 loops) (86 lines)
       From: Dennis Diskin <diskin.dennis@KENDLE.COM>
     • Re: Trouble with a SAS "DO" Statement (21 x 21 x 21 x 21 loops) (74 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: Trouble with a SAS "DO" Statement (21 x 21 x 21 x 21 loops) (76 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: Trouble with a SAS "DO" Statement (21 x 21 x 21 x 21 loops) (74 lines)
       From: lpogoda <lpogoda@HOTMAIL.COM>

114. User asked for termination
     • User asked for termination (89 lines)
       From: SAS User <sas@SDAC.HARVARD.EDU>
     • Re: User asked for termination (133 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • Re: User asked for termination (146 lines)
       From: SAS User <sas@SDAC.HARVARD.EDU>
     • Re: User asked for termination (49 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • Re: User asked for termination (92 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>

115. User asked for termination (Thanks)
     • Re: User asked for termination (Thanks) (61 lines)
       From: SAS User <sas@SDAC.HARVARD.EDU>
     • Re: User asked for termination (Thanks) (81 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>

116. Validating Phone Numbers
     • Validating Phone Numbers (19 lines)
       From: 0101 htns <htns0101@YAHOO.COM>
     • Re: Validating Phone Numbers (53 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: Validating Phone Numbers (40 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: Validating Phone Numbers (62 lines)
       From: Toby Dunn <tdunn@OAKHILLTECH.COM>
     • Re: Validating Phone Numbers (16 lines)
       From: 0101 htns <htns0101@YAHOO.COM>
     • Re: Validating Phone Numbers (52 lines)
       From: Karsten M. Self <kmself@IX.NETCOM.COM>
     • Re: Validating Phone Numbers (16 lines)
       From: 0101 htns <htns0101@YAHOO.COM>
     • Re: Validating Phone Numbers (79 lines)
       From: sreevatsan <sreevat.s@GLOBALCASE.NET>
     • Re: Validating Phone Numbers (74 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • Re: Validating Phone Numbers (85 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>

117. Variable creation
     • Variable creation (20 lines)
       From: Peter <murderx@MAIL333.COM>
     • Re: Variable creation (57 lines)
       From: Dennis Diskin <diskin.dennis@KENDLE.COM>
     • Re: Variable creation (24 lines)
       From: Jay Weedon <jweedon@EARTHLINK.NET>
     • Re: Variable creation (25 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: Variable creation (33 lines)
       From: Peter <murderx@MAIL333.COM>

118. Viewtable
     • Re: Viewtable (84 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

119. What's wrong with this:
     • Re: What's wrong with this: (29 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

120. What's wrong with this: street_n=addr1_1|" "||addr2||" "||addr3||" "||addr4||" "||addr5
     • What's wrong with this: street_n=addr1_1|" "||addr2||" "||addr3||" "||addr4||" "||addr5 (50 lines)
       From: Duck-Hye Yang <dyang@CHAPINHALL.ORG>
     • Re: What's wrong with this: street_n=addr1_1|" "||addr2||" "||addr3||" "||addr4||" "||addr5 (21 lines)
       From: Charles Patridge <charles_s_patridge@PRODIGY.NET>
     • Re: What's wrong with this: street_n=addr1_1|" "||addr2||" "||addr3||" "||addr4||" "||addr5 (65 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: What's wrong with this: street_n=addr1_1|" "||addr2||" "||addr3||" "||addr4||" "||addr5 (53 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: What's wrong with this: street_n=addr1_1|" "||addr2||" "||addr3||" "||addr4||" "||addr5 (77 lines)
       From: Duck-Hye Yang <dyang@CHAPINHALL.ORG>
     • Re: What's wrong with this: street_n=addr1_1|" "||addr2||" "||addr3||" "||addr4||" "||addr5 (14 lines)
       From: Arto Raiskio <arto-nospam@RAISKIO.COM>

121. Why DATEPART function is not working
     • Why DATEPART function is not working (32 lines)
       From: Anbu Arasu <aarumugam@STTHOMAS.EDU>
     • Re: Why DATEPART function is not working (68 lines)
       From: Don & Susann <don_stanley@PARADISE.NET.NZ>
     • Re: Why DATEPART function is not working (41 lines)
       From: Lars Wahlgren <lars.wahlgren.pleasenospam@STAT.LU.SE>
     • Re: Why DATEPART function is not working (50 lines)
       From: Lars Wahlgren <lars.wahlgren.pleasenospam@STAT.LU.SE>
     • Re: Why DATEPART function is not working (66 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

122. Would An Extra Paycheck Next Month Help iz vzctfrz wi
     • Would An Extra Paycheck Next Month Help iz vzctfrz wi (83 lines)
       From: Lorena Watson <iantibus@FIREMAIL.DE>

123. Writing to flat files on Unix
     • Re: Writing to flat files on Unix (111 lines)
       From: Karsten M. Self <kmself@IX.NETCOM.COM>

124. X Axis in Proc Gplot
     • X Axis in Proc Gplot (51 lines)
       From: Yanal Ansouqa <ansouqa@SBCGLOBAL.NET>
     • Re: X Axis in Proc Gplot (58 lines)
       From: Yanal Ansouqa <ansouqa@SBCGLOBAL.NET>

125. [Q] Interpretation of dimensions in Correspondence Analysis
     • [Q] Interpretation of dimensions in Correspondence Analysis (19 lines)
       From: Mark AC Emmett <markacemmett@AOL.COM>

126. census data on user friendly CD
     • census data on user friendly CD (16 lines)
       From: Doug McAllaster <doug_mcallaster@HARCOURT.COM>
     • Re: census data on user friendly CD (65 lines)
       From: Michael S. Zdeb <msz03@HEALTH.STATE.NY.US>
     • Re: census data on user friendly CD (35 lines)
       From: William W. Viergever <wwvierg@ATTGLOBAL.NET>

127. come check out this exclusive footage
     • come check out this exclusive footage (19 lines)
       From: Karen L. Woodruff <k.woodruff_yy@AOL.COM>

128. counting by-groups
     • counting by-groups (27 lines)
       From: Gerard <brian_boru@ATT.NET>
     • Re: counting by-groups (40 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • Re: counting by-groups (60 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: counting by-groups (28 lines)
       From: m n <iced_phoenix@YAHOO.COM>

129. detecting changes in data
     • detecting changes in data (95 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>
     • Re: detecting changes in data (152 lines)
       From: Nat Wooding <Nathaniel_Wooding@DOM.COM>
     • Re: detecting changes in data (124 lines)
       From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
     • Re: detecting changes in data (158 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>
     • Re: detecting changes in data (193 lines)
       From: Dennis Diskin <diskin.dennis@KENDLE.COM>
     • Re: detecting changes in data (199 lines)
       From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
     • Re: detecting changes in data (213 lines)
       From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
     • Re: detecting changes in data (121 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • Re: detecting changes in data (109 lines)
       From: Charles Harbour <harbourcharles@JOHNDEERE.COM>
     • Re: detecting changes in data (107 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>

130. employment
     • employment (32 lines)
       From: Kevin Auslander <kausland77@HOTMAIL.COM>

131. graphics
     • graphics (64 lines)
       From: Carlos Tadeu <ctsdias@CARPA.CIAGRI.USP.BR>

132. help
     • help (20 lines)
       From: Zhonghe Li <zli@HSPH.HARVARD.EDU>

133. help SAS/MS ACCESS, general database questions
     • help SAS/MS ACCESS, general database questions (58 lines)
       From: Rob Cheshire <rob.cheshire@NOAA.GOV>
     • Re: help SAS/MS ACCESS, general database questions (74 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • Re: help SAS/MS ACCESS, general database questions (108 lines)
       From: Charles Harbour <harbourcharles@JOHNDEERE.COM>
     • Re: help SAS/MS ACCESS, general database questions (92 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

134. how its working? (Modified list input)
     • how its working? (Modified list input) (41 lines)
       From: kanthan <airaha_m@REDIFFMAIL.COM>
     • Re: how its working? (Modified list input) (70 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: how its working? (Modified list input) (55 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: how its working? (Modified list input) (88 lines)
       From: kanthan <airaha_m@REDIFFMAIL.COM>
     • Re: how its working? (Modified list input) (99 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: how its working? (Modified list input) (195 lines)
       From: kanthan <airaha_m@REDIFFMAIL.COM>

135. how to use sql coalesce with time
     • how to use sql coalesce with time (68 lines)
       From: Arto Raiskio <arto-nospam@RAISKIO.COM>
     • Re: how to use sql coalesce with time (77 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: how to use sql coalesce with time (124 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: how to use sql coalesce with time (21 lines)
       From: Arto Raiskio <arto-nospam@RAISKIO.COM>

136. insert data into db
     • Re: insert data into db (40 lines)
       From: Giz Tariku <GizT@MSN.COM>

137. macro parameter foolishness
     • Re: macro parameter foolishness (55 lines)
       From: Mike Rhoads <RHOADSM1@WESTAT.COM>
     • Re: macro parameter foolishness (61 lines)
       From: =?koi8-r?Q?=22?=sas hole=?koi8-r?Q?=22=20?= <sashole@MAIL.RU>
     • Re: macro parameter foolishness (58 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: macro parameter foolishness (87 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: macro parameter foolishness (121 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: macro parameter foolishness (53 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>

138. men growth enlarge ur manhood
     • men growth enlarge ur manhood (18 lines)
       From: Sofia Rojas <rojas_df@YAHOO.COM>

139. nlp query
     • nlp query (27 lines)
       From: Regi <regivm123@YAHOO.COM>
     • Re: nlp query (35 lines)
       From: Jay Weedon <jweedon@EARTHLINK.NET>

140. obtain external file date/time
     • Re: obtain external file date/time (18 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

141. output sum of vars to a file
     • output sum of vars to a file (77 lines)
       From: Jamil Ibrahim <jibrahim@IR.UMSMED.EDU>
     • Re: output sum of vars to a file (89 lines)
       From: Don Stanley <don_stanley@PARADISE.NET.NZ>
     • Re: output sum of vars to a file (129 lines)
       From: Nat Wooding <Nathaniel_Wooding@DOM.COM>

142. pound sign causes macro problems in Version 9.1
     • Re: pound sign causes macro problems in Version 9.1 (60 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>
     • Re: pound sign causes macro problems in Version 9.1 (23 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>

143. proc discrim - nonparametric
     • proc discrim - nonparametric (34 lines)
       From: Vincent <vincent.jones@REDGULL.BIZ>

144. proc format question
     • proc format question (33 lines)
       From: PD <sophe88@YAHOO.COM>
     • Re: proc format question (44 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>
     • Re: proc format question (43 lines)
       From: Don Stanley <don_stanley@PARADISE.NET.NZ>
     • Re: proc format question (55 lines)
       From: PD <sophe88@YAHOO.COM>

145. proc import truncating
     • proc import truncating (16 lines)
       From: saslist@COMCAST.NET
     • Re: proc import truncating (33 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>

146. proc sql question
     • proc sql question (31 lines)
       From: David FIckbohm <davefickbohm@YAHOO.COM>
     • Re: proc sql question (71 lines)
       From: Roger Lustig <trovato@VERIZON.NET>

147. raw data reading problem
     • raw data reading problem (78 lines)
       From: Chris <chris.goller@BANKOFAMERICA.COM>
     • Re: raw data reading problem (134 lines)
       From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
     • Re: raw data reading problem (133 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: raw data reading problem (9 lines)
       From: Chris Goller <chris.goller@BANKOFAMERICA.COM>

148. read about super H`G`H even better then normal H^G_H - srxdgkxardsscr
     • read about super H`G`H even better then normal H^G_H - srxdgkxardsscr (43 lines)
       From: Myron Brandt <myron.brandtns@SYO.FI>

149. reading part data
     • reading part data (20 lines)
       From: Sun Bow <sunbow4u@HOTMAIL.COM>
     • Re: reading part data (44 lines)
       From: Nitin Chandak <nitin.chandak@GLOBALCASE.NET>
     • Re: reading part data (39 lines)
       From: Kevin Roland Viel <kviel@EMORY.EDU>
     • Re: reading part data (51 lines)
       From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>

150. removal from List (Out of office)
     • removal from List (Out of office) (24 lines)
       From: F. J. Kelley <jkelley@UGA.EDU>

151. remove "table of" generated by the freq procedure in ods html
     • remove "table of" generated by the freq procedure in ods html (33 lines)
       From: Xavier Autret <xav_x@NOOS.FR>
     • Re: remove "table of" generated by the freq procedure in ods html (68 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>

152. sas access - dbms
     • sas access - dbms (33 lines)
       From: Andre Wielki <wielki@INED.FR>

153. select part of the text in the program editor and submit it
     • select part of the text in the program editor and submit it (10 lines)
       From: Erik Christiansen <ec@SELVMORDSFORSKNING.DK>
     • Re: select part of the text in the program editor and submit it (34 lines)
       From: Fehd, Ronald J. (PHPPO) <rjf2@CDC.GOV>
     • Re: select part of the text in the program editor and submit it (25 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: select part of the text in the program editor and submit it (31 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>

154. syntax/reference for proc neural
     • syntax/reference for proc neural (15 lines)
       From: rick <rick_member@NEWSGUY.COM>

155. tab character as delimiter
     • tab character as delimiter (15 lines)
       From: Sanford Lefkowitz <slefkowit@CAS.ORG>
     • Re: tab character as delimiter (31 lines)
       From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM>
     • Re: tab character as delimiter (47 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: tab character as delimiter (26 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: tab character as delimiter (33 lines)
       From: Tarbash Patel a.k.a. Babu <epidemiologist@SCIENTIST.COM>

156. test post
     • test post (10 lines)
       From: rmengis@YCI.COM

157. test post, please ignore
     • test post, please ignore (15 lines)
       From: Skinner, Deborah <Deborah.Skinner@ASSURANT.COM>

158. trial interaction
     • trial interaction (35 lines)
       From: jms <pitybeetwk@HOTMAIL.COM>

159. two-stage and fixed effects?
     • two-stage and fixed effects? (23 lines)
       From: S. Sneeringer <ssneeringer@HOTMAIL.COM>

160. unsubscribe
     • unsubscribe (11 lines)
       From: Ranjeet Gauni <ranjeetg@HOTMAIL.COM>

161. using ODS to export to XLS problem......
     • using ODS to export to XLS problem...... (40 lines)
       From: Ixnay <mscgloss@YAHOO.COM>
     • Re: using ODS to export to XLS problem...... (60 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: using ODS to export to XLS problem...... (28 lines)
       From: Arto Raiskio <arto-nospam@RAISKIO.COM>
     • Re: using ODS to export to XLS problem...... (61 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: using ODS to export to XLS problem...... (27 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: using ODS to export to XLS problem...... (44 lines)
       From: Delaney, Kevin P. <khd8@CDC.GOV>
     • Re: using ODS to export to XLS problem...... (59 lines)
       From: Nitin Chandak <nitin.chandak@GLOBALCASE.NET>

162. what is the expansion for DSD?
     • what is the expansion for DSD? (16 lines)
       From: kanthan <airaha_m@REDIFFMAIL.COM>
     • Re: what is the expansion for DSD? (35 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: what is the expansion for DSD? (69 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • Re: what is the expansion for DSD? (18 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: what is the expansion for DSD? (54 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: what is the expansion for DSD? (28 lines)
       From: Walter Scott <Walter.Scott@STATE.TN.US>
     • Re: what is the expansion for DSD? (49 lines)
       From: Toby Dunn <tdunn@OAKHILLTECH.COM>
     • Re: what is the expansion for DSD? (33 lines)
       From: Arjen Raateland <arjen.raateland@YMPARISTO.FI>
     • Re: what is the expansion for DSD? (41 lines)
       From: Kirsty Lauderdale <kirsty.lauderdale@EUROPE.PPDI.COM>
     • Re: what is the expansion for DSD? (27 lines)
       From: D. Einstadter <deinstadter@METROHEALTH.ORG>
     • Re: what is the expansion for DSD? (15 lines)
       From: kanthan <airaha_m@REDIFFMAIL.COM>