Table of contents:

• $73221
• $91823 (2 messages)
• %SYSFUNC and PUT function (12 messages)
• %include with return code to calling program --> is this possible? (6 messages)
• 9.1.2 documentation for a stand-alone machine (4 messages)
• =?GB2312?B?xvPStc34u+62r82o1qqjrLKiy83E+iA2zfLK176tteQ=?= MP3 =?GB2312?B?1NrP38rUzP2joQ==?=
• =?gb2312?B?W9XQxrhdIEJpb3N0YXRpc3RpY2lhbi9TQVMgUHJvZ3JhbW1lciBPcA==?= =?gb2312?B?cG9ydHVuaXR5IA==?=
• ANOVA procedure for 3 levels repeated measures (2 messages)
• ASSISTANCE(BUSINESS PROPOSAL!!!
• ATTENTION/
• AWARD NOTIFICATION
• About new SAS Miner & guide (2 messages)
• Be a more enormous gent
• Best way to Include data and time in a filename (6 messages)
• Biostatistics JOB
• Br.eaking Ne.ws - CSJJ in Ne.gotiations to Acq.uire 35% in BioMedicom Inc 121
• CONGRATS YOU WON (LUCKY STRIKE LOTTERY).
• CONGRATULATION!!!
• CONGRATULATION.
• CONGRATULATIONS LUCKY WINNER OF THE YEAR
• CONGRATULATIONS!!!
• CONGRATULATIONS!!!!
• CONGRATULATIONS!!!!!
• Call for Papers - Feature and Variable Selection
• Can you change the font size within a data null? Other sugges tions?
• Can you change the font size within a data null? Other suggestions? (3 messages)
• Can you change the font size within a data null? Othersuggestions?
• Can you read an SQL image type field into SAS? (3 messages)
• Congratulations you are the Winner of our lottery and your fund is ready for collection
• Contact me urgently (2 messages)
• DEAR FRIEND
• Discriminant
• Do Loop in a macro numbers files and variables (6 messages)
• Do you want a change?
• DoW Loop "Duh" experience - data set and infile N+1 loops
• DoW Loop "Duh" experience - data set and infile N+1loops (5 messages)
• Dynamic Variable Problem, Help!!! (4 messages)
• Email marketing
• Enterprise Guide in Pharma/ CRO?
• FOR YOUR CONSIDERATION
• FPOINT() and FWRITE() in UPDATE mode ! (2 messages)
• FROM COUTHER AND MOTHER
• FROM MARIAM ABACHA & FAMILY FOUNDATION
• FROM MRS. MARYAM ABACHA.
• FW: Iterative proportional fitting
• Forcing Quotes for Output of DSD Character Values (3 messages)
• Friedman's test - SUGI 12? (4 messages)
• From Mac Johnson Bonida, Liberia West Africa
• GOOD DAY
• GREECE 2004 OLYMPIC EMAIL LOTTERY NOTIFICATION!
• Get XLPI Tuesday Morning For HUGE Profits cot
• Good Macro programming practice? (2 messages)
• Gplot Kill SAS Session, Why? (5 messages)
• Guttman Scaling? (2 messages)
• HELLO
• HOLAP MDDB Registration thru SCL
• Haaaardeeeeeeer Ereeectiooooooons
• Hello
• Help in creating and analyzing a Bradley-Terry model for paired comparisons (2 messages)
• Help with By group processing, thanks (20 messages)
• Hokki =)
• How do I write an SQL query using dataset observations? (8 messages)
• How to Erase old file and write on it (4 messages)
• How to Keep Menu bar inside SAS/AF application (3 messages)
• How to Unsusbcrib from SAS-L@VM.MARIST.EDU
• IF conditions and ARRAY subscripts (5 messages)
• Independent Random Numbers (4 messages)
• Interacting with the web (6 messages)
• Is there any way I can see what a Macro does (6 messages)
• Iterative proportional fitting (3 messages)
• JUST FOR YOUR INTEREST
• Lesbian Beastiality 1509
• Lesbian Beastiality 7926
• Looking for general ideas on how to approach a user interface sel ection process (3 messages)
• Lose 19%, powerful weightloss now available where you are. (3 messages)
• MAILER DEMON. Mail not sent. ID: rosterPortland:underling
• MDDB or repository problem (2 messages)
• Macro Question (5 messages)
• Macro not working in SAS/CONNECT.
• Macro/no macro challenge (3 messages)
• Missing value in PROC FREQ (3 messages)
• My Girlfriend Naked 8068
• My Girlfriends Huge Nipples 5656
• My Girlfriends Huge Nipples 9303
• My girlfriend in a wet white bra 2830
• My girlfriend in a wet white bra 4427
• My girlfriend in a wet white bra 4636
• My girlfriends nipples pokeing out of her wet bra 2491
• NOTIFICATION (2 messages)
• New question: passing in parameters to macro (newbie question)
• ODS EMAIL and Content-Transfer-Encoding (3 messages)
• OT: ASCII code inventor dies (21 messages)
• OT: STAT-L (was Re: Professional Language? (4 messages)
• OUR PHAR`MACY HAS GREAT WEEK:LY SPECIALS -" ssuaisbfriom
• One merge with different groups (2 messages)
• Online Pharmacy - Lowest Prices - Viagra and More! ...
• PLEASE CONTACT ME IMMEDIATELY
• PLEASE ENDEAVOUR TO USE FOR GODS CHILDREN.
• PROC EXPAND / time series recs when dates are missing (4 messages)
• PROC MIXED OR PROC MODEL (GMM)
• PROC SORT: nodups versus nodupkey (13 messages)
• PharmaSUG 2005 (3 messages)
• Pickup observations by keyword (2 messages)
• Placing the page numbre in a pdf document
• Poisson: adding variation (4 messages)
• Preserve spaces in PROC TABULATE (2 messages)
• Problems to read unstructured text into a dataset (3 messages)
• Problems to run macros containing data-commands with a loop (8 messages)
• Proc SQl vs DB2 Question (2 messages)
• Professional Language? (6 messages)
• Progress bar (7 messages)
• Promote for You
• Q: number of significant characters in value or format with SORT and FREQ
• Question Regd. FILENAME() function and FILE statement. (2 messages)
• R e: %SYSFUNC and PUT function
• RE : Forcing Quotes for Output of DSD Character Values
• RE : PROC EXPAND / time series recs when dates are missing
• RE : SAS/IML subroutine - LMS/LTS
• RE : starting excel and decimal point
• RESPOND SINCERELY
• Read SQL image field using SAS
• Regression Modeling - Interaction Term (2 messages)
• Romainian Teenagers Raped. Banned Photos. 3687
• Romainian Teenagers Raped. Banned Photos. 6137
• Romainian Teenagers Raped. Banned Photos. 9272
• Réf. : Unwanted "stair-stepping" in PROC REPORT output (3 messages)
• SAS (V8 and above) under XP (8 messages)
• SAS Connect, multiple users - suggestions wanted (3 messages)
• SAS Date Interval (2 messages)
• SAS Generated GIFs to Directory Structure (messy question) (5 messages)
• SAS portability (5 messages)
• SAS procedure SHEWHART ? (5 messages)
• SAS(r) Seminars in Washington, DC July 2004
• SAS/Graph (2 messages)
• SAS/IML subroutine - LMS/LTS (2 messages)
• SAS: The One-Day Course
• SESUG '04 Conference Information Now Available
• SQL Server and DTS
• STAT-L (was Re: Professional Language? (3 messages)
• Sas date comparison of number of days between two months star ting on first of month to id reporting period
• Sas date comparison of number of days between two months starting on first of month to id reporting period (3 messages)
• Sas date comparison of number of days between twomonths starting on first of month to id reporting period (2 messages)
• Simpsons characters like Maggie drinking sex juices
• Soliciting For Partnership.
• Spending TOO MUCH on Prescriptions?
• Subqueries (2 messages)
• Suppress cell counts in PROC TABULATE? (4 messages)
• Survival Analysis Course, July 12-16, July 26-30
• The Fountain of Youth
• The One-Day Course
• Trick for Mass Renaming of Variables (7 messages)
• URGENT REQUEST.
• Undocumented feature in Proc SQL to select duplicate observat ions (3 messages)
• Undocumented feature in Proc SQL to select duplicate observations (7 messages)
• Unwanted "stair-stepping" in PROC REPORT output (2 messages)
• Up 300% in days - check the next one out " dnpcdlbkhblf
• Using one table to look up values in another
• WE SHIIP WORLDWIDE ORIGINAL SOFTWARES AT CHEAP summer mind
• WINNING NOTIFICATION.
• What does this function do (6 messages)
• What is wrong with this code ? (5 messages)
• What the heck is UPPER()? (17 messages)
• What's the best solution to do many to many merge? Thanks! (8 messages)
• What's the best solution to do many to many merge?Thanks!
• When a merge fails but SQL does not - 'Merge GotCha'
• White Heteroskedasticity - ACOV (3 messages)
• Winsorization (4 messages)
• YOU HAVE WON A LOTTO
• YOUR LOTTERY AWARD WINNING NOTIFCATION
• Your lotto Winning acknowledgement Note
• ZIP for dummies
• arrangements of indistinguishable objects? (4 messages)
• arrows (3 messages)
• attn: Stop to risk your life. alleles
• attn: Stop to risk your life. roster
• automatically delete the file and Over write on it (2 messages)
• clearing macro variable from memory (5 messages)
• coding problem (3 messages)
• comparing two groups' mean (4 messages)
• counter for percent agreement (4 messages)
• creating sequential id (3 messages)
• debrief: SAS Breakthru Tour (7 messages)
• dfbetas
• enIarge your p-e-n-l-s anything kilohm
• enterprise guide and XP login (2 messages)
• gS_gE_gX adventures! regulators beefing
• hope to hear from you
• how do you display Proc Summary timedata ? (2 messages)
• how to increase width of formats for some characters variables? (4 messages)
• kappa (2 messages)
• load SAS table into DB2 temporary table
• long string -> hex -> decimal (6 messages)
• macro variable holding more than one value - problem defined clearly
• macros
• newbie question (4 messages)
• passing in parameters to macro (newbie question) (7 messages)
• phreg and var1*var2 (interaction variables) (3 messages)
• problem solved
• proc spl question (2 messages)
• question on format of datetime hours (2 messages)
• read a large flat file (7 messages)
• repeated measures, correlation between parities
• reply pls!!!
• residuals in regression analysis
• sas menu
• starting excel and decimal point (2 messages)
• sur in syslin (2 messages)
• this offer is yours
• unequal spacing, Proc MIXED (2 messages)
• value with an ampersand (6 messages)
• x0pjb

1. $73221
   • $73221 (28 lines)
     From: Leon Lovell <leonlovell_fp@PTT.NET.PH>

2. $91823
   • $91823 (27 lines)
     From: Carole Crocker <c_crocker_jh@MEMYAM.DINOCO.DE>
   • $91823 (27 lines)
     From: Eugenio Conklin <e.conklinwu@KLINIK-VALENS.CH>

3. %SYSFUNC and PUT function
   • %SYSFUNC and PUT function (26 lines)
     From: Talbot Michael Katz <topkatz@MSN.COM>
   • Re: %SYSFUNC and PUT function (56 lines)
     From: Harry Droogendyk <harry.droogendyk@RBC.COM>
   • Re: %SYSFUNC and PUT function (67 lines)
     From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
   • Re: %SYSFUNC and PUT function (11 lines)
     From: Talbot Michael Katz <topkatz@MSN.COM>
   • Re: %SYSFUNC and PUT function (30 lines)
     From: Buchanan, Gordon <gordon.buchanan@GMACRFC.COM>
   • Re: %SYSFUNC and PUT function (20 lines)
     From: Talbot Michael Katz <topkatz@MSN.COM>
   • Re: %SYSFUNC and PUT function (61 lines)
     From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
   • Re: %SYSFUNC and PUT function (97 lines)
     From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
   • Re: %SYSFUNC and PUT function (128 lines)
     From: Paul M. Dorfman <sashole@BELLSOUTH.NET>
   • Re: %SYSFUNC and PUT function (130 lines)
     From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
   • Re: %SYSFUNC and PUT function (102 lines)
     From: Guido <cymraeg_erict@HOTMAIL.COM>
   • Re: %SYSFUNC and PUT function (137 lines)
     From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>

4. %include with return code to calling program --> is this possible?
   • %include with return code to calling program --> is this possible? (35 lines)
     From: Sober Hi <soberhi@YAHOO.COM>
   • Re: %include with return code to calling program --> is this possible? (41 lines)
     From: Jim Groeneveld <jim.groeneveld@VITATRON.COM>
   • Re: %include with return code to calling program --> is this possible? (60 lines)
     From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
   • Re: %include with return code to calling program --> is this possible? (62 lines)
     From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
   • Re: %include with return code to calling program --> is this possible? (79 lines)
     From: Sober Hi <soberhi@YAHOO.COM>
   • Re: %include with return code to calling program --> is this possible? (80 lines)
     From: Leo Chan <leo.y.h.chan@GRADUATE.HKU.HK>

5. 9.1.2 documentation for a stand-alone machine
   • 9.1.2 documentation for a stand-alone machine (13 lines)
     From: Bruce Bradbury <BruceBrad@INAME.COM>
   • Re: 9.1.2 documentation for a stand-alone machine (36 lines)
     From: SUBSCRIBE SAS-L Stephane <datametric@CLUB-INTERNET.FR>
   • Re: 9.1.2 documentation for a stand-alone machine (26 lines)
     From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
   • Re: 9.1.2 documentation for a stand-alone machine (18 lines)
     From: Bruce Bradbury <BruceBrad@INAME.COM>

6. =?GB2312?B?xvPStc34u+62r82o1qqjrLKiy83E+iA2zfLK176tteQ=?= MP3 =?GB2312?B?1NrP38rUzP2joQ==?=
   • =?GB2312?B?xvPStc34u+62r82o1qqjrLKiy83E+iA2zfLK176tteQ=?= MP3 =?GB2312?B?1NrP38rUzP2joQ==?= (32 lines)
     From: =?GB2312?B?tqvEz8bz0rXN+A==?= <webmaster@WWW.CN>

7. =?gb2312?B?W9XQxrhdIEJpb3N0YXRpc3RpY2lhbi9TQVMgUHJvZ3JhbW1lciBPcA==?= =?gb2312?B?cG9ydHVuaXR5IA==?=
   • =?gb2312?B?W9XQxrhdIEJpb3N0YXRpc3RpY2lhbi9TQVMgUHJvZ3JhbW1lciBPcA==?= =?gb2312?B?cG9ydHVuaXR5IA==?= (71 lines)
     From: Zibao Zhang <zibaozhang@HOTMAIL.COM>

8. ANOVA procedure for 3 levels repeated measures
   • ANOVA procedure for 3 levels repeated measures (19 lines)
     From: Sam Gu <sasprof@HOTMAIL.COM>
   • Re: ANOVA procedure for 3 levels repeated measures (71 lines)
     From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

9. ASSISTANCE(BUSINESS PROPOSAL!!!
   • ASSISTANCE(BUSINESS PROPOSAL!!! (24 lines)
     From: GUEI_3GE <GUEI_3GE@TELSTRA.COM>

10. ATTENTION/
    • ATTENTION/ (57 lines)
      From: George Raphael <georgeraphael@INDIATIMES.COM>

11. AWARD NOTIFICATION
    • AWARD NOTIFICATION (67 lines)
      From: markkessjohn@TELSTRA.COM

12. About new SAS Miner & guide
    • About new SAS Miner & guide (42 lines)
      From: Datametric <datametric@CLUB-INTERNET.FR>
    • About new SAS Miner & guide (40 lines)
      From: SUBSCRIBE SAS-L Stephane <datametric@CLUB-INTERNET.FR>

13. Be a more enormous gent
    • Be a more enormous gent (60 lines)
      From: Kennith Fraser <wtvbneyryrnx@PRIVAT.WEB-ART.DE>

14. Best way to Include data and time in a filename
    • Best way to Include data and time in a filename (26 lines)
      From: David Fickbohm <DavidF@HOMEGAIN.COM>
    • Re: Best way to Include data and time in a filename (35 lines)
      From: bogdan romocea <br44092@GAWAB.COM>
    • Re: Best way to Include data and time in a filename (77 lines)
      From: Terjeson, Mark <TERJEM@DSHS.WA.GOV>
    • Re: Best way to Include data and time in a filename (50 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Best way to Include data and time in a filename (62 lines)
      From: Harry Droogendyk <harry.droogendyk@RBC.COM>
    • Re: Best way to Include data and time in a filename (128 lines)
      From: Shawn Edney <Edney.Shawn@EPAMAIL.EPA.GOV>

15. Biostatistics JOB
    • Biostatistics JOB (31 lines)
      From: R Scherzer <scherzer.@PROSOF.COM>

16. Br.eaking Ne.ws - CSJJ in Ne.gotiations to Acq.uire 35% in BioMedicom Inc 121
    • Br.eaking Ne.ws - CSJJ in Ne.gotiations to Acq.uire 35% in BioMedicom Inc 121 (79 lines)
      From: Chris Kay <glaluocbhz@HKSTAR.COM>

17. CONGRATS YOU WON (LUCKY STRIKE LOTTERY).
    • CONGRATS YOU WON (LUCKY STRIKE LOTTERY). (89 lines)
      From: lottocoord <lottocoordinator2004@YAHOO.CO.UK>

18. CONGRATULATION!!!
    • CONGRATULATION!!! (70 lines)
      From: LOTTERY PROMOTION <goldenlottery@EASYINFOMAIL.CO.ZA>

19. CONGRATULATION.
    • CONGRATULATION. (69 lines)
      From: LOTTERY NOTIFICATION. <goldenlottery77@NETSCAPE.NET>

20. CONGRATULATIONS LUCKY WINNER OF THE YEAR
    • CONGRATULATIONS LUCKY WINNER OF THE YEAR (36 lines)
      From: dora_sivie777 <dora_sivie777@TELSTRA.COM>

21. CONGRATULATIONS!!!
    • CONGRATULATIONS!!! (82 lines)
      From: lotto <lottoeuropean@TISCALI.CO.UK>

22. CONGRATULATIONS!!!!
    • CONGRATULATIONS!!!! (86 lines)
      From: reneealex@FLORIDAGATORS.COM

23. CONGRATULATIONS!!!!!
    • CONGRATULATIONS!!!!! (51 lines)
      From: EURO STATE LOTTERY <eurostate@PHANTOMEMAIL.COM>

24. Call for Papers - Feature and Variable Selection
    • Call for Papers - Feature and Variable Selection (86 lines)
      From: Leonardo Auslender <Leonardo.Auslender@SAS.COM>

25. Can you change the font size within a data null? Other sugges tions?
    • Re: Can you change the font size within a data null? Other sugges tions? (59 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>

26. Can you change the font size within a data null? Other suggestions?
    • Can you change the font size within a data null? Other suggestions? (37 lines)
      From: Talbot Michael Katz <topkatz@MSN.COM>
    • Re: Can you change the font size within a data null? Other suggestions? (90 lines)
      From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
    • Re: Can you change the font size within a data null? Other suggestions? (18 lines)
      From: Steve Raimi <steven.raimi@GM.COM>

27. Can you change the font size within a data null? Othersuggestions?
    • Re: Can you change the font size within a data null? Othersuggestions? (86 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>

28. Can you read an SQL image type field into SAS?
    • Can you read an SQL image type field into SAS? (11 lines)
      From: Marc <mschless@ADELPHIA.NET>
    • Re: Can you read an SQL image type field into SAS? (33 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: Can you read an SQL image type field into SAS? (27 lines)
      From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

29. Congratulations you are the Winner of our lottery and your fund is ready for collection
    • Congratulations you are the Winner of our lottery and your fund is ready for collection (59 lines)
      From: info_grouplotto@MAIL2WEBMASTER.COM

30. Contact me urgently
    • Contact me urgently (59 lines)
      From: Mr.Steve William <steve22william@YATHOO.COM>
    • Contact me urgently (59 lines)
      From: Mr.Poroko Aruga <ruga@YATHOO.COM>

31. DEAR FRIEND
    • DEAR FRIEND (42 lines)
      From: davidowolabi3 <davidowolabi3@LAHAONLINE.COM>

32. Discriminant
    • Discriminant (21 lines)
      From: Sajeel <sajeelmanzoor@HOTMAIL.COM>

33. Do Loop in a macro numbers files and variables
    • Do Loop in a macro numbers files and variables (104 lines)
      From: Pat Moore <anpam@UAA.ALASKA.EDU>
    • Re: Do Loop in a macro numbers files and variables (233 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
    • Re: Do Loop in a macro numbers files and variables (92 lines)
      From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
    • Re: Do Loop in a macro numbers files and variables (92 lines)
      From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
    • Re: Do Loop in a macro numbers files and variables (145 lines)
      From: Matt <mness@AMGEN.COM>
    • Re: Do Loop in a macro numbers files and variables (92 lines)
      From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>

34. Do you want a change?
    • Do you want a change? (24 lines)
      From: Willard Scruggs <wscruggs_pc@EXCITE.COM>

35. DoW Loop "Duh" experience - data set and infile N+1 loops
    • DoW Loop "Duh" experience - data set and infile N+1 loops (228 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>

36. DoW Loop "Duh" experience - data set and infile N+1loops
    • Re: DoW Loop "Duh" experience - data set and infile N+1loops (285 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
    • Re: DoW Loop "Duh" experience - data set and infile N+1loops (191 lines)
      From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
    • Re: DoW Loop "Duh" experience - data set and infile N+1loops (216 lines)
      From: Paul M. Dorfman <sashole@BELLSOUTH.NET>
    • Re: DoW Loop "Duh" experience - data set and infile N+1loops (406 lines)
      From: Paul M. Dorfman <sashole@BELLSOUTH.NET>
    • Re: DoW Loop "Duh" experience - data set and infile N+1loops (28 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>

37. Dynamic Variable Problem, Help!!!
    • Dynamic Variable Problem, Help!!! (35 lines)
      From: John J. Gilroy <jjgilroy@HOUSEHOLD.COM>
    • Re: Dynamic Variable Problem, Help!!! (77 lines)
      From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
    • Re: Dynamic Variable Problem, Help!!! (43 lines)
      From: Kevin Roland Viel <kviel@EMORY.EDU>
    • Re: Dynamic Variable Problem, Help!!! (49 lines)
      From: Ian Whitlock <iw1junk@COMCAST.NET>

38. Email marketing
    • Email marketing (180 lines)
      From: bn@hotmail.com <bn@HOTMAIL.COM>

39. Enterprise Guide in Pharma/ CRO?
    • Enterprise Guide in Pharma/ CRO? (34 lines)
      From: novastaylor@GMAIL.COM

40. FOR YOUR CONSIDERATION
    • FOR YOUR CONSIDERATION (29 lines)
      From: MRS. PATRICA KOVAC <dfghh@HOTMAIL.COM>

41. FPOINT() and FWRITE() in UPDATE mode !
    • FPOINT() and FWRITE() in UPDATE mode ! (120 lines)
      From: kanthan <airaha_m@REDIFFMAIL.COM>
    • Re: FPOINT() and FWRITE() in UPDATE mode ! (135 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

42. FROM COUTHER AND MOTHER
    • FROM COUTHER AND MOTHER (46 lines)
      From: COUTHER SAVIMBI <couthersavimbi@NETSCAPE.NET>

43. FROM MARIAM ABACHA & FAMILY FOUNDATION
    • FROM MARIAM ABACHA & FAMILY FOUNDATION (73 lines)
      From: maryam_aba4u <maryam_aba4u@LIBERO.IT>

44. FROM MRS. MARYAM ABACHA.
    • FROM MRS. MARYAM ABACHA. (80 lines)
      From: m_abacha14@VIRGILIO.IT

45. FW: Iterative proportional fitting
    • FW: Iterative proportional fitting (78 lines)
      From: Zack, Matthew M. <MMZ1@CDC.GOV>

46. Forcing Quotes for Output of DSD Character Values
    • Forcing Quotes for Output of DSD Character Values (28 lines)
      From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
    • Re: Forcing Quotes for Output of DSD Character Values (66 lines)
      From: Roger DeAngelis <xlr82sas@AOL.COM>
    • Re: Forcing Quotes for Output of DSD Character Values (67 lines)
      From: Paul M. Dorfman <sashole@BELLSOUTH.NET>

47. Friedman's test - SUGI 12?
    • Friedman's test - SUGI 12? (24 lines)
      From: Dennis G. Fisher <dfisher@CSULB.EDU>
    • Re: Friedman's test - SUGI 12? (47 lines)
      From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
    • Re: Friedman's test - SUGI 12? (74 lines)
      From: Dennis G. Fisher <dfisher@CSULB.EDU>
    • Re: Friedman's test - SUGI 12? (32 lines)
      From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

48. From Mac Johnson Bonida, Liberia West Africa
    • From Mac Johnson Bonida, Liberia West Africa (32 lines)
      From: mjohnsonbonida <mjohnsonbonida@TELSTRA.COM>

49. GOOD DAY
    • GOOD DAY (42 lines)
      From: dr salas tatu <salas_505@TISCALI.CO.UK>

50. GREECE 2004 OLYMPIC EMAIL LOTTERY NOTIFICATION!
    • GREECE 2004 OLYMPIC EMAIL LOTTERY NOTIFICATION! (77 lines)
      From: GREECE 2004 INTERNATIONAL E-MAIL LOTTERY. <goldenlotto@EASYINFOMAIL.CO.ZA>

51. Get XLPI Tuesday Morning For HUGE Profits cot
    • Get XLPI Tuesday Morning For HUGE Profits cot (72 lines)
      From: Vincenza Bugh <hmqsusoqe@DSN.T-KOUGEI.AC.JP>

52. Good Macro programming practice?
    • Good Macro programming practice? (55 lines)
      From: Roger DeAngelis <xlr82sas@AOL.COM>
    • Re: Good Macro programming practice? (48 lines)
      From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>

53. Gplot Kill SAS Session, Why?
    • Gplot Kill SAS Session, Why? (95 lines)
      From: Pleasant, David (GE Consumer Finance) <David.Pleasant@GE.COM>
    • Re: Gplot Kill SAS Session, Why? (120 lines)
      From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
    • Re: Gplot Kill SAS Session, Why? (13 lines)
      From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
    • Re: Gplot Kill SAS Session, Why? (154 lines)
      From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK>
    • Re: Gplot Kill SAS Session, Why? (175 lines)
      From: Rene Valverde <valverde-venturare@LILLY.COM>

54. Guttman Scaling?
    • Guttman Scaling? (24 lines)
      From: Dennis G. Fisher <dfisher@CSULB.EDU>
    • Re: Guttman Scaling? (41 lines)
      From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

55. HELLO
    • HELLO (40 lines)
      From: frankhassan22@QUICK.CZ

56. HOLAP MDDB Registration thru SCL
    • Re: HOLAP MDDB Registration thru SCL (23 lines)
      From: GetMe <getmeeazy@YAHOO.COM>

57. Haaaardeeeeeeer Ereeectiooooooons
    • Haaaardeeeeeeer Ereeectiooooooons (68 lines)
      From: Jonah Hearn <DLOJQXPGJZTR@ITL.NET.UA>

58. Hello
    • Hello (71 lines)
      From: Mr. John Camara <johncamara32@ZWALLET.COM>

59. Help in creating and analyzing a Bradley-Terry model for paired comparisons
    • Help in creating and analyzing a Bradley-Terry model for paired comparisons (57 lines)
      From: Cornel Lencar <clencar@INTERCHANGE.UBC.CA>
    • Help in creating and analyzing a Bradley-Terry model for paired comparisons (76 lines)
      From: Cornel Lencar <clencar@INTERCHANGE.UBC.CA>

60. Help with By group processing, thanks
    • Help with By group processing, thanks (69 lines)
      From: SAS L <sasluser@YAHOO.COM>
    • Re: Help with By group processing, thanks (93 lines)
      From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
    • Re: Help with By group processing, thanks (117 lines)
      From: Nordlund, Dan <NordlDJ@DSHS.WA.GOV>
    • Re: Help with By group processing, thanks (145 lines)
      From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
    • Re: Help with By group processing, thanks (93 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: Help with By group processing, thanks (91 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Help with By group processing, thanks (122 lines)
      From: Paul M. Dorfman <sashole@BELLSOUTH.NET>
    • Re: Help with By group processing, thanks (144 lines)
      From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
    • Re: Help with By group processing, thanks (193 lines)
      From: Paul M. Dorfman <sashole@BELLSOUTH.NET>
    • Re: Help with By group processing, thanks (81 lines)
      From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
    • Re: Help with By group processing, thanks (487 lines)
      From: David Gelb <djgelb@HOTMAIL.COM>
    • Re: Help with By group processing, thanks (107 lines)
      From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
    • Re: Help with By group processing, thanks (111 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: Help with By group processing, thanks (50 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Help with By group processing, thanks (29 lines)
      From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
    • Re: Help with By group processing, thanks (162 lines)
      From: Paul M. Dorfman <sashole@BELLSOUTH.NET>
    • Re: Help with By group processing, thanks (203 lines)
      From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
    • Re: Help with By group processing, thanks (221 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: Help with By group processing, thanks (30 lines)
      From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
    • Re: Help with By group processing, thanks (46 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

61. Hokki =)
    • Hokki =) (12 lines)
      From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>

62. How do I write an SQL query using dataset observations?
    • How do I write an SQL query using dataset observations? (41 lines)
      From: ben.powell@CLA.CO.UK
    • Re: How do I write an SQL query using dataset observations? (69 lines)
      From: ben.powell@CLA.CO.UK
    • Re: How do I write an SQL query using dataset observations? (83 lines)
      From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
    • Re: How do I write an SQL query using dataset observations? (97 lines)
      From: Ben Powell <Ben.powell@CLA.CO.UK>
    • Re: How do I write an SQL query using dataset observations? (67 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: How do I write an SQL query using dataset observations? (29 lines)
      From: Nina Harris <sas@MAILINATOR.COM>
    • Re: How do I write an SQL query using dataset observations? (98 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: How do I write an SQL query using dataset observations? (116 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>

63. How to Erase old file and write on it
    • How to Erase old file and write on it (19 lines)
      From: kumar <subramanyam_22@YAHOO.COM>
    • Re: How to Erase old file and write on it (38 lines)
      From: Jim Groeneveld <jim.groeneveld@VITATRON.COM>
    • Re: How to Erase old file and write on it (52 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
    • Re: How to Erase old file and write on it (52 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>

64. How to Keep Menu bar inside SAS/AF application
    • How to Keep Menu bar inside SAS/AF application (19 lines)
      From: kumar <subramanyam_22@YAHOO.COM>
    • Re: How to Keep Menu bar inside SAS/AF application (58 lines)
      From: Workman, Rob <Rob.Workman@CARBOMEDICS.COM>
    • Re: How to Keep Menu bar inside SAS/AF application (48 lines)
      From: Randy Herbison <RandyHerbison@WESTAT.COM>

65. How to Unsusbcrib from SAS-L@VM.MARIST.EDU
    • How to Unsusbcrib from SAS-L@VM.MARIST.EDU (11 lines)
      From: Elmaache, Hamani <Hamani.Elmaache@CCRA-ADRC.GC.CA>

66. IF conditions and ARRAY subscripts
    • IF conditions and ARRAY subscripts (43 lines)
      From: Talbot Michael Katz <topkatz@MSN.COM>
    • Re: IF conditions and ARRAY subscripts (30 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
    • Re: IF conditions and ARRAY subscripts (109 lines)
      From: Paul M. Dorfman <sashole@BELLSOUTH.NET>
    • Re: IF conditions and ARRAY subscripts (22 lines)
      From: Talbot Michael Katz <topkatz@MSN.COM>
    • Re: IF conditions and ARRAY subscripts (65 lines)
      From: Paul M. Dorfman <sashole@BELLSOUTH.NET>

67. Independent Random Numbers
    • Independent Random Numbers (17 lines)
      From: Bruce Bradbury <BruceBrad@INAME.COM>
    • Re: Independent Random Numbers (48 lines)
      From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Independent Random Numbers (47 lines)
      From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
    • Re: Independent Random Numbers (43 lines)
      From: Richard Ristow <wrristow@MINDSPRING.COM>

68. Interacting with the web
    • Interacting with the web (21 lines)
      From: Lou <lpogodajr292185@COMCAST.NET>
    • Re: Interacting with the web (52 lines)
      From: Alan Churchill <EmailMeDirectly@THISWEBSITE-ERRATIX.US>
    • Re: Interacting with the web (94 lines)
      From: Lou <lpogodajr292185@COMCAST.NET>
    • Re: Interacting with the web (83 lines)
      From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
    • Re: Interacting with the web (51 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
    • Re: Interacting with the web (133 lines)
      From: Alan Churchill <EmailMeDirectly@THISWEBSITE-ERRATIX.US>

69. Is there any way I can see what a Macro does
    • Is there any way I can see what a Macro does (15 lines)
      From: kumar <subramanyam_22@YAHOO.COM>
    • Re: Is there any way I can see what a Macro does (70 lines)
      From: Paul M. Dorfman <sashole@BELLSOUTH.NET>
    • Re: Is there any way I can see what a Macro does (20 lines)
      From: Jim Groeneveld <jim.groeneveld@VITATRON.COM>
    • Re: Is there any way I can see what a Macro does (62 lines)
      From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
    • Re: Is there any way I can see what a Macro does (96 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
    • Re: Is there any way I can see what a Macro does (193 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>

70. Iterative proportional fitting
    • Iterative proportional fitting (63 lines)
      From: DTP <null@VOID.COM>
    • Re: Iterative proportional fitting (41 lines)
      From: DTP <null@VOID.COM>
    • Re: Iterative proportional fitting (74 lines)
      From: Zack, Matthew M. <MMZ1@CDC.GOV>

71. JUST FOR YOUR INTEREST
    • JUST FOR YOUR INTEREST (47 lines)
      From: MARTINS BILLARD <EURO_LEGAL@REDIFFMAIL.COM>

72. Lesbian Beastiality 1509
    • Lesbian Beastiality 1509 (9 lines)
      From: kjones@BLUEYONDER.CO.UK

73. Lesbian Beastiality 7926
    • Lesbian Beastiality 7926 (10 lines)
      From: franbaker@CG.SHAWCABLE.NET

74. Looking for general ideas on how to approach a user interface sel ection process
    • Looking for general ideas on how to approach a user interface sel ection process (46 lines)
      From: David Fickbohm <DavidF@HOMEGAIN.COM>
    • Re: Looking for general ideas on how to approach a user interface sel ection process (26 lines)
      From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
    • Re: Looking for general ideas on how to approach a user interface sel ection process (65 lines)
      From: Alan Churchill <EmailMeDirectly@THISWEBSITE-ERRATIX.US>

75. Lose 19%, powerful weightloss now available where you are.
    • Lose 19%, powerful weightloss now available where you are. (34 lines)
      From: Sofia Givens <sofiagivens_bw@STI.CA>
    • Lose 19%, powerful weightloss now available where you are. (34 lines)
      From: Lenora Weaver <lenoraweaver_wc@GLOLINK.CO.ZA>
    • Lose 19%, powerful weightloss now available where you are. (36 lines)
      From: Barbra Meadows <barbrameadows_xu@CNAC-GP.FR>

76. MAILER DEMON. Mail not sent. ID: rosterPortland:underling
    • Re: MAILER DEMON. Mail not sent. ID: rosterPortland:underling (27 lines)
      From: Hubertus.gregor <alexstringers@EASTMAIL.COM>

77. MDDB or repository problem
    • MDDB or repository problem (22 lines)
      From: Simon Gillow <sgillow@LINEONE.NET>
    • Re: MDDB or repository problem (51 lines)
      From: Don Henderson <donaldjhenderson@HOTMAIL.COM>

78. Macro Question
    • Macro Question (24 lines)
      From: Ross, Michael D <michael.ross@ASTRAZENECA.COM>
    • Re: Macro Question (44 lines)
      From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
    • Re: Macro Question (61 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
    • Re: Macro Question (33 lines)
      From: Ross, Michael D <michael.ross@ASTRAZENECA.COM>
    • Re: Macro Question (101 lines)
      From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>

79. Macro not working in SAS/CONNECT.
    • Re: Macro not working in SAS/CONNECT. (318 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>

80. Macro/no macro challenge
    • Re: Macro/no macro challenge (207 lines)
      From: Ian Whitlock <iw1junk@COMCAST.NET>
    • Re: Macro/no macro challenge (186 lines)
      From: Ian Whitlock <iw1junk@COMCAST.NET>
    • Re: Macro/no macro challenge (345 lines)
      From: Ian Whitlock <iw1junk@COMCAST.NET>

81. Missing value in PROC FREQ
    • Missing value in PROC FREQ (369 lines)
      From: 0101 htns <htns0101@YAHOO.COM>
    • Re: Missing value in PROC FREQ (26 lines)
      From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
    • Re: Missing value in PROC FREQ (36 lines)
      From: 0101 htns <htns0101@YAHOO.COM>

82. My Girlfriend Naked 8068
    • My Girlfriend Naked 8068 (10 lines)
      From: jasonscott@ED.SHAWCABLE.NET

83. My Girlfriends Huge Nipples 5656
    • My Girlfriends Huge Nipples 5656 (10 lines)
      From: jasonscott@ED.SHAWCABLE.NET

84. My Girlfriends Huge Nipples 9303
    • My Girlfriends Huge Nipples 9303 (9 lines)
      From: leepaterson@BLUEYONDER.CO.UK

85. My girlfriend in a wet white bra 2830
    • My girlfriend in a wet white bra 2830 (11 lines)
      From: davidtaylor@OPTONLINE.NET

86. My girlfriend in a wet white bra 4427
    • My girlfriend in a wet white bra 4427 (11 lines)
      From: petergrass@HOUSTON.RR.COM

87. My girlfriend in a wet white bra 4636
    • My girlfriend in a wet white bra 4636 (11 lines)
      From: davidh@SC.RR.COM

88. My girlfriends nipples pokeing out of her wet bra 2491
    • My girlfriends nipples pokeing out of her wet bra 2491 (10 lines)
      From: johndavis@VN.SHAWCABLE.NET

89. NOTIFICATION
    • NOTIFICATION (112 lines)
      From: southprotea2003 <southprotea2003@YAHOO.COM>
    • NOTIFICATION (59 lines)
      From: ashleycoleman206 <ashleycoleman206@FREEZONE.CO.UK>

90. New question: passing in parameters to macro (newbie question)
    • New question: passing in parameters to macro (newbie question) (58 lines)
      From: K*F <kafernan@UWATERLOO.CA>

91. ODS EMAIL and Content-Transfer-Encoding
    • Re: ODS EMAIL and Content-Transfer-Encoding (46 lines)
      From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
    • Re: ODS EMAIL and Content-Transfer-Encoding (56 lines)
      From: bogdan romocea <br44092@GAWAB.COM>
    • Re: ODS EMAIL and Content-Transfer-Encoding (79 lines)
      From: Allan B. Christensen <abc@DK2NET.DK>

92. OT: ASCII code inventor dies
    • OT: ASCII code inventor dies (10 lines)
      From: Miller, Jeremy T. <zyp9@CDC.GOV>
    • Re: OT: ASCII code inventor dies (25 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
    • Re: OT: ASCII code inventor dies (40 lines)
      From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
    • Re: OT: ASCII code inventor dies (50 lines)
      From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
    • Re: OT: ASCII code inventor dies (49 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: OT: ASCII code inventor dies (68 lines)
      From: F. J. Kelley <jkelley@UGA.EDU>
    • Re: OT: ASCII code inventor dies (70 lines)
      From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
    • Re: OT: ASCII code inventor dies (17 lines)
      From: Peter Flom <flom@NDRI.ORG>
    • Re: OT: ASCII code inventor dies (35 lines)
      From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM>
    • Re: OT: ASCII code inventor dies (89 lines)
      From: Baxley, Robert Edwin <BAXLEYR@MAIL.ETSU.EDU>
    • Re: OT: ASCII code inventor dies (120 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
    • Re: OT: ASCII code inventor dies (28 lines)
      From: Michael S. Zdeb <msz03@HEALTH.STATE.NY.US>
    • Re: OT: ASCII code inventor dies (38 lines)
      From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
    • Re: OT: ASCII code inventor dies (26 lines)
      From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
    • Re: OT: ASCII code inventor dies (55 lines)
      From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
    • Re: OT: ASCII code inventor dies (67 lines)
      From: Lustig, Roger <roger.lustig@CITIGROUP.COM>
    • Re: OT: ASCII code inventor dies (57 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
    • Re: OT: ASCII code inventor dies (49 lines)
      From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
    • Re: OT: ASCII code inventor dies (36 lines)
      From: Richard Ristow <wrristow@MINDSPRING.COM>
    • Re: OT: ASCII code inventor dies (33 lines)
      From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
    • Re: OT: ASCII code inventor dies (49 lines)
      From: Walter Scott <Walter.Scott@STATE.TN.US>

93. OT: STAT-L (was Re: Professional Language?
    • OT: STAT-L (was Re: Professional Language? (22 lines)
      From: Jerry Davis <jwd@GRIFFIN.UGA.EDU>
    • Re: OT: STAT-L (was Re: Professional Language? (54 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
    • Re: OT: STAT-L (was Re: Professional Language? (38 lines)
      From: F. J. Kelley <jkelley@UGA.EDU>
    • Re: OT: STAT-L (was Re: Professional Language? (70 lines)
      From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>

94. OUR PHAR`MACY HAS GREAT WEEK:LY SPECIALS -" ssuaisbfriom
    • OUR PHAR`MACY HAS GREAT WEEK:LY SPECIALS -" ssuaisbfriom (35 lines)
      From: Vanessa Marcum <v.marcumme@MODI.IT>

95. One merge with different groups
    • One merge with different groups (37 lines)
      From: Thomas <tythong@YAHOO.COM>
    • Re: One merge with different groups (93 lines)
      From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>

96. Online Pharmacy - Lowest Prices - Viagra and More! ...
    • Online Pharmacy - Lowest Prices - Viagra and More! ... (23 lines)
      From: Marquis G. Boggs <g.boggsdm@HOTMAIL.COM>

97. PLEASE CONTACT ME IMMEDIATELY
    • PLEASE CONTACT ME IMMEDIATELY (42 lines)
      From: fred_taylor2000@TELSTRA.COM

98. PLEASE ENDEAVOUR TO USE FOR GODS CHILDREN.
    • PLEASE ENDEAVOUR TO USE FOR GODS CHILDREN. (77 lines)
      From: hjmary@TISCALI.CO.UK

99. PROC EXPAND / time series recs when dates are missing
    • PROC EXPAND / time series recs when dates are missing (47 lines)
      From: Karen Olson <karen.olson@TCH.HARVARD.EDU>
    • Re: PROC EXPAND / time series recs when dates are missing (96 lines)
      From: Terjeson, Mark <TERJEM@DSHS.WA.GOV>
    • Re: PROC EXPAND / time series recs when dates are missing (35 lines)
      From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
    • Re: PROC EXPAND / time series recs when dates are missing (17 lines)
      From: Karen Olson <karen.olson@TCH.HARVARD.EDU>

100. PROC MIXED OR PROC MODEL (GMM)
     • PROC MIXED OR PROC MODEL (GMM) (19 lines)
       From: Thomas <tythong@YAHOO.COM>

101. PROC SORT: nodups versus nodupkey
     • PROC SORT: nodups versus nodupkey (20 lines)
       From: Kimberly LeBouton <kimberly.lebouton@VERIZON.NET>
     • Re: PROC SORT: nodups versus nodupkey (29 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: PROC SORT: nodups versus nodupkey (69 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>
     • Re: PROC SORT: nodups versus nodupkey (76 lines)
       From: Lou <lpogodajr292185@COMCAST.NET>
     • Re: PROC SORT: nodups versus nodupkey (47 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
     • Re: PROC SORT: nodups versus nodupkey (34 lines)
       From: Lou <lpogodajr292185@COMCAST.NET>
     • Re: PROC SORT: nodups versus nodupkey (61 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
     • Re: PROC SORT: nodups versus nodupkey (95 lines)
       From: lpogoda <lpogoda@HOTMAIL.COM>
     • Re: PROC SORT: nodups versus nodupkey (18 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • Re: PROC SORT: nodups versus nodupkey (52 lines)
       From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
     • Re: PROC SORT: nodups versus nodupkey (92 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • Re: PROC SORT: nodups versus nodupkey (35 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
     • Re: PROC SORT: nodups versus nodupkey (153 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

102. PharmaSUG 2005
     • PharmaSUG 2005 (24 lines)
       From: Kevin Roland Viel <kviel@EMORY.EDU>
     • Re: PharmaSUG 2005 (40 lines)
       From: Brian Shilling <bshilling@A-CI.COM>
     • Re: PharmaSUG 2005 (39 lines)
       From: Nancy Brucken <brucken@PROVIDE.NET>

103. Pickup observations by keyword
     • Pickup observations by keyword (35 lines)
       From: Thomas <tythong@YAHOO.COM>
     • Re: Pickup observations by keyword (64 lines)
       From: Steve Raimi <steven.raimi@GM.COM>

104. Placing the page numbre in a pdf document
     • Placing the page numbre in a pdf document (68 lines)
       From: GOMEZ TEJERINA, PEDRO ALBERTO <PEDRO.GOMEZ@GRUPOBBVA.COM>

105. Poisson: adding variation
     • Poisson: adding variation (36 lines)
       From: Jeffrey Stratford <stratja@AUBURN.EDU>
     • Re: Poisson: adding variation (40 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
     • Re: Poisson: adding variation (60 lines)
       From: Peter Flom <flom@NDRI.ORG>
     • Re: Poisson: adding variation (95 lines)
       From: Dale McLerran <stringplayer_2@YAHOO.COM>

106. Preserve spaces in PROC TABULATE
     • Preserve spaces in PROC TABULATE (26 lines)
       From: Brian Shilling <bshilling@A-CI.COM>
     • Re: Preserve spaces in PROC TABULATE (61 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>

107. Problems to read unstructured text into a dataset
     • Problems to read unstructured text into a dataset (148 lines)
       From: Rune Runnestoe <rune@FASTLANE.NO>
     • Re: Problems to read unstructured text into a dataset (209 lines)
       From: Alan Churchill <EmailMeDirectly@THISWEBSITE-ERRATIX.US>
     • Re: Problems to read unstructured text into a dataset (171 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>

108. Problems to run macros containing data-commands with a loop
     • Problems to run macros containing data-commands with a loop (46 lines)
       From: Marcel_Eberle <marceleberle@MY-MAIL.CH>
     • Re: Problems to run macros containing data-commands with a loop (70 lines)
       From: SUBSCRIBE SAS-L Stephane <datametric@CLUB-INTERNET.FR>
     • Re: Problems to run macros containing data-commands with a loop (52 lines)
       From: RolandRB <rolandberry@HOTMAIL.COM>
     • Re: Problems to run macros containing data-commands with a loop (61 lines)
       From: Christian Lensbjerg <christian.lensbjerg@ALMBRAND.DK>
     • Re: Problems to run macros containing data-commands with a loop (104 lines)
       From: SUBSCRIBE SAS-L Stephane <datametric@CLUB-INTERNET.FR>
     • Re: Problems to run macros containing data-commands with a loop (21 lines)
       From: Marcel_Eberle <marceleberle@MY-MAIL.CH>
     • Re: Problems to run macros containing data-commands with a loop (35 lines)
       From: Charles Harbour <harbourcharles@JOHNDEERE.COM>
     • Re: Problems to run macros containing data-commands with a loop (61 lines)
       From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>

109. Proc SQl vs DB2 Question
     • Re: Proc SQl vs DB2 Question (198 lines)
       From: ben.powell@CLA.CO.UK
     • Re: Proc SQl vs DB2 Question (217 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

110. Professional Language?
     • Professional Language? (28 lines)
       From: Bill Wagenseller <william.wagenseller@US.SANOFI.COM>
     • Re: Professional Language? (55 lines)
       From: F. J. Kelley <jkelley@UGA.EDU>
     • Re: Professional Language? (71 lines)
       From: Paul M. Dorfman <sashole@BELLSOUTH.NET>
     • Re: Professional Language? (30 lines)
       From: F. J. Kelley <jkelley@UGA.EDU>
     • Re: Professional Language? (16 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: Professional Language? (64 lines)
       From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>

111. Progress bar
     • Progress bar (60 lines)
       From: GOMEZ TEJERINA, PEDRO ALBERTO <PEDRO.GOMEZ@GRUPOBBVA.COM>
     • Re: Progress bar (70 lines)
       From: Christian Lensbjerg <christian.lensbjerg@ALMBRAND.DK>
     • Re: Progress bar (23 lines)
       From: Robert Walls <robert.walls@EUROPE.PPDI.COM>
     • Re: Progress bar (69 lines)
       From: Lex Jansen <spam@LEXJANSEN.COM>
     • Re: Progress bar (56 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: Progress bar (31 lines)
       From: Pedro Gómez <pedro.gomez@GRUPOBBVA.COM>
     • Re: Progress bar (30 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

112. Promote for You
     • Promote for You (43 lines)
       From: Tom <Senderlist@CITIZ.NET>

113. Q: number of significant characters in value or format with SORT and FREQ
     • Q: number of significant characters in value or format with SORT and FREQ (33 lines)
       From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>

114. Question Regd. FILENAME() function and FILE statement.
     • Question Regd. FILENAME() function and FILE statement. (54 lines)
       From: kanthan <airaha_m@REDIFFMAIL.COM>
     • Re: Question Regd. FILENAME() function and FILE statement. (141 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>

115. R e: %SYSFUNC and PUT function
     • R e: %SYSFUNC and PUT function (35 lines)
       From: Guido <cymraeg_erict@HOTMAIL.COM>

116. RE : Forcing Quotes for Output of DSD Character Values
     • RE : Forcing Quotes for Output of DSD Character Values (66 lines)
       From: Datametric <datametric@CLUB-INTERNET.FR>

117. RE : PROC EXPAND / time series recs when dates are missing
     • RE : PROC EXPAND / time series recs when dates are missing (67 lines)
       From: Datametric <datametric@CLUB-INTERNET.FR>

118. RE : SAS/IML subroutine - LMS/LTS
     • RE : SAS/IML subroutine - LMS/LTS (60 lines)
       From: Datametric <datametric@CLUB-INTERNET.FR>

119. RE : starting excel and decimal point
     • RE : starting excel and decimal point (66 lines)
       From: Datametric <datametric@CLUB-INTERNET.FR>

120. RESPOND SINCERELY
     • RESPOND SINCERELY (46 lines)
       From: GETTIS <forexlcom@YAHOO.ES>

121. Read SQL image field using SAS
     • Read SQL image field using SAS (11 lines)
       From: Marc <mschless@ADELPHIA.NET>

122. Regression Modeling - Interaction Term
     • Regression Modeling - Interaction Term (38 lines)
       From: Thomas <tythong@YAHOO.COM>
     • Re: Regression Modeling - Interaction Term (97 lines)
       From: Peter Flom <flom@NDRI.ORG>

123. Romainian Teenagers Raped. Banned Photos. 3687
     • Romainian Teenagers Raped. Banned Photos. 3687 (10 lines)
       From: leefranks@BLUEYONDER.CO.UK

124. Romainian Teenagers Raped. Banned Photos. 6137
     • Romainian Teenagers Raped. Banned Photos. 6137 (11 lines)
       From: fbarker@WP.SHAWCABLE.NET

125. Romainian Teenagers Raped. Banned Photos. 9272
     • Romainian Teenagers Raped. Banned Photos. 9272 (10 lines)
       From: leefranks@BLUEYONDER.CO.UK

126. Réf. : Unwanted "stair-stepping" in PROC REPORT output
     • Re: Réf. : Unwanted "stair-stepping" in PROC REPORT output (16 lines)
       From: Bob Abelson <Bob_Abelson@HGSI.COM>
     • Re: Réf. : Unwanted "stair-stepping" in PROC REPORT output (19 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • Re: Réf. : Unwanted "stair-stepping" in PROC REPORT output (46 lines)
       From: Bob Abelson <Bob_Abelson@HGSI.COM>

127. SAS (V8 and above) under XP
     • SAS (V8 and above) under XP (17 lines)
       From: Peter T. Manolakos <ptmanolakos@HOTMAIL.COM>
     • Re: SAS (V8 and above) under XP (26 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: SAS (V8 and above) under XP (32 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: SAS (V8 and above) under XP (37 lines)
       From: Droogendyk, Harry <harry.droogendyk@RBC.COM>
     • Re: SAS (V8 and above) under XP (41 lines)
       From: Tim Braam <timothy.j.braam@CENSUS.GOV>
     • Re: SAS (V8 and above) under XP (27 lines)
       From: Alan Churchill <EmailMeDirectly@THISWEBSITE-ERRATIX.US>
     • Re: SAS (V8 and above) under XP (19 lines)
       From: Peter T. Manolakos <ptmanolakos@HOTMAIL.COM>
     • Re: SAS (V8 and above) under XP (53 lines)
       From: Doug <dougie_cam@HOTMAIL.COM>

128. SAS Connect, multiple users - suggestions wanted
     • SAS Connect, multiple users - suggestions wanted (25 lines)
       From: Buchanan, Gordon <gordon.buchanan@GMACRFC.COM>
     • Re: SAS Connect, multiple users - suggestions wanted (66 lines)
       From: Phil Rack <philrack@MINEQUEST.COM>
     • Re: SAS Connect, multiple users - suggestions wanted (55 lines)
       From: bogdan romocea <br44092@GAWAB.COM>

129. SAS Date Interval
     • SAS Date Interval (33 lines)
       From: Rick Preiss <rpreiss@PREISSCO.COM>
     • Re: SAS Date Interval (71 lines)
       From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>

130. SAS Generated GIFs to Directory Structure (messy question)
     • SAS Generated GIFs to Directory Structure (messy question) (77 lines)
       From: Carl Kyonka <Carl.Kyonka@ENBRIDGE.COM>
     • Re: SAS Generated GIFs to Directory Structure (messy question) (101 lines)
       From: bogdan romocea <br44092@GAWAB.COM>
     • Re: SAS Generated GIFs to Directory Structure (messy question) (131 lines)
       From: Huang, Ya <yhuang@AMYLIN.COM>
     • Re: SAS Generated GIFs to Directory Structure (messy question) (76 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
     • Re: SAS Generated GIFs to Directory Structure (messy question) (102 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

131. SAS portability
     • SAS portability (14 lines)
       From: Pradeep <mbpradeep@GMAIL.COM>
     • Re: SAS portability (17 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
     • Re: SAS portability (29 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
     • Re: SAS portability (32 lines)
       From: Pradeep <mbpradeep@GMAIL.COM>
     • Re: SAS portability (65 lines)
       From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>

132. SAS procedure SHEWHART ?
     • SAS procedure SHEWHART ? (39 lines)
       From: Wright, Wendi <wwright@ETS.ORG>
     • Re: SAS procedure SHEWHART ? (55 lines)
       From: DePuy, Venita <depuy001@DCRI.DUKE.EDU>
     • Re: SAS procedure SHEWHART ? (7 lines)
       From: Steve Raimi <steven.raimi@GM.COM>
     • Re: SAS procedure SHEWHART ? (53 lines)
       From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM>
     • Re: SAS procedure SHEWHART ? (39 lines)
       From: Paul Kairis <kairis@COX.NET>

133. SAS(r) Seminars in Washington, DC July 2004
     • SAS(r) Seminars in Washington, DC July 2004 (42 lines)
       From: Andrew H. Karp <sfbay0001@AOL.COMNOPE>

134. SAS/Graph
     • Re: SAS/Graph (23 lines)
       From: Nina Harris <sas@MAILINATOR.COM>
     • Re: SAS/Graph (37 lines)
       From: Peter Flom <flom@NDRI.ORG>

135. SAS/IML subroutine - LMS/LTS
     • SAS/IML subroutine - LMS/LTS (30 lines)
       From: Thomas <tythong@YAHOO.COM>
     • Re: SAS/IML subroutine - LMS/LTS (70 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

136. SAS: The One-Day Course
     • SAS: The One-Day Course (19 lines)
       From: Michael S. Zdeb <msz03@HEALTH.STATE.NY.US>

137. SESUG '04 Conference Information Now Available
     • SESUG '04 Conference Information Now Available (41 lines)
       From: SESUG INFORMATION <sesuginc@UGA.EDU>

138. SQL Server and DTS
     • SQL Server and DTS (40 lines)
       From: Alan Churchill <EmailMeDirectly@THISWEBSITE-ERRATIX.US>

139. STAT-L (was Re: Professional Language?
     • Re: STAT-L (was Re: Professional Language? (62 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: STAT-L (was Re: Professional Language? (86 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: STAT-L (was Re: Professional Language? (33 lines)
       From: Jim Groeneveld <jim.groeneveld@VITATRON.COM>

140. Sas date comparison of number of days between two months star ting on first of month to id reporting period
     • Re: Sas date comparison of number of days between two months star ting on first of month to id reporting period (85 lines)
       From: Terjeson, Mark <TERJEM@DSHS.WA.GOV>

141. Sas date comparison of number of days between two months starting on first of month to id reporting period
     • Sas date comparison of number of days between two months starting on first of month to id reporting period (26 lines)
       From: Fred <kukulkan248@MSN.COM>
     • Re: Sas date comparison of number of days between two months starting on first of month to id reporting period (64 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: Sas date comparison of number of days between two months starting on first of month to id reporting period (42 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>

142. Sas date comparison of number of days between twomonths starting on first of month to id reporting period
     • Re: Sas date comparison of number of days between twomonths starting on first of month to id reporting period (41 lines)
       From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
     • Re: Sas date comparison of number of days between twomonths starting on first of month to id reporting period (73 lines)
       From: Fred <kukulkan248@MSN.COM>

143. Simpsons characters like Maggie drinking sex juices
     • Simpsons characters like Maggie drinking sex juices (26 lines)
       From: Out <andgently@TOONS-X.COM>

144. Soliciting For Partnership.
     • Soliciting For Partnership. (26 lines)
       From: aarronkennedy2001@TELSTRA.COM

145. Spending TOO MUCH on Prescriptions?
     • Spending TOO MUCH on Prescriptions? (23 lines)
       From: Geoffrey Adkins <gadkinsky@AYA.OFFICE.NE.JP>

146. Subqueries
     • Subqueries (23 lines)
       From: Nicole Bibb <nicole.d.bibb@WELLSFARGO.COM>
     • Re: Subqueries (36 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>

147. Suppress cell counts in PROC TABULATE?
     • Suppress cell counts in PROC TABULATE? (29 lines)
       From: David Hanna <dhanna@HEALTH.NYC.GOV>
     • Re: Suppress cell counts in PROC TABULATE? (70 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: Suppress cell counts in PROC TABULATE? (91 lines)
       From: David Hanna <dhanna@HEALTH.NYC.GOV>
     • Re: Suppress cell counts in PROC TABULATE? (35 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

148. Survival Analysis Course, July 12-16, July 26-30
     • Survival Analysis Course, July 12-16, July 26-30 (14 lines)
       From: Paul Allison <allison@SOC.UPENN.EDU>

149. The Fountain of Youth
     • The Fountain of Youth (23 lines)
       From: Penelope L. Purcell <p.lpurcell_ch@ANALYTIC.CH>

150. The One-Day Course
     • Re: The One-Day Course (46 lines)
       From: Paul M. Dorfman <sashole@BELLSOUTH.NET>

151. Trick for Mass Renaming of Variables
     • Trick for Mass Renaming of Variables (43 lines)
       From: Kevin Myers <KevinMyers@AUSTIN.RR.COM>
     • Re: Trick for Mass Renaming of Variables (149 lines)
       From: Paul M. Dorfman <sashole@BELLSOUTH.NET>
     • Re: Trick for Mass Renaming of Variables (89 lines)
       From: Jim Groeneveld <jim.groeneveld@VITATRON.COM>
     • Re: Trick for Mass Renaming of Variables (76 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: Trick for Mass Renaming of Variables (159 lines)
       From: thierry <thierrydecae@HOTMAIL.COM>
     • Re: Trick for Mass Renaming of Variables (120 lines)
       From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
     • Re: Trick for Mass Renaming of Variables (135 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>

152. URGENT REQUEST.
     • URGENT REQUEST. (78 lines)
       From: mrjohneso@SUNUMAIL.SN

153. Undocumented feature in Proc SQL to select duplicate observat ions
     • Re: Undocumented feature in Proc SQL to select duplicate observat ions (100 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • Re: Undocumented feature in Proc SQL to select duplicate observat ions (146 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • Re: Undocumented feature in Proc SQL to select duplicate observat ions (272 lines)
       From: Roger DeAngelis <xlr82sas@AOL.COM>

154. Undocumented feature in Proc SQL to select duplicate observations
     • Undocumented feature in Proc SQL to select duplicate observations (11 lines)
       From: Max Cherny <chernym@YAHOO.COM>
     • Re: Undocumented feature in Proc SQL to select duplicate observations (24 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: Undocumented feature in Proc SQL to select duplicate observations (50 lines)
       From: Don Henderson <donaldjhenderson@HOTMAIL.COM>
     • Re: Undocumented feature in Proc SQL to select duplicate observations (41 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: Undocumented feature in Proc SQL to select duplicate observations (98 lines)
       From: Don Henderson <donaldjhenderson@HOTMAIL.COM>
     • Re: Undocumented feature in Proc SQL to select duplicate observations (140 lines)
       From: Roger DeAngelis <xlr82sas@AOL.COM>
     • Re: Undocumented feature in Proc SQL to select duplicate observations (119 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>

155. Unwanted "stair-stepping" in PROC REPORT output
     • Unwanted "stair-stepping" in PROC REPORT output (79 lines)
       From: Bob Abelson <Bob_Abelson@HGSI.COM>
     • Re: Unwanted "stair-stepping" in PROC REPORT output (103 lines)
       From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>

156. Up 300% in days - check the next one out " dnpcdlbkhblf
     • Up 300% in days - check the next one out " dnpcdlbkhblf (33 lines)
       From: Robbie Forrest <robbieforrest_wx@CIGES.INF.CU>

157. Using one table to look up values in another
     • Re: Using one table to look up values in another (178 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>

158. WE SHIIP WORLDWIDE ORIGINAL SOFTWARES AT CHEAP summer mind
     • WE SHIIP WORLDWIDE ORIGINAL SOFTWARES AT CHEAP summer mind (12 lines)
       From: Griselda Mirtha <ixq5qcxhu@LASER.NET>

159. WINNING NOTIFICATION.
     • WINNING NOTIFICATION. (42 lines)
       From: globallottery0004@TELSTRA.COM

160. What does this function do
     • What does this function do (18 lines)
       From: kumar <subramanyam_22@YAHOO.COM>
     • Re: What does this function do (35 lines)
       From: DePuy, Venita <depuy001@DCRI.DUKE.EDU>
     • Re: What does this function do (30 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • Re: What does this function do (34 lines)
       From: Randy Herbison <RandyHerbison@WESTAT.COM>
     • Re: What does this function do (44 lines)
       From: Quentin McMullen <quentin_mcmullen@BROWN.EDU>
     • Re: What does this function do (89 lines)
       From: Paul M. Dorfman <sashole@BELLSOUTH.NET>

161. What is wrong with this code ?
     • What is wrong with this code ? (126 lines)
       From: Rune Runnestoe <rune@FASTLANE.NO>
     • Re: What is wrong with this code ? (156 lines)
       From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
     • Re: What is wrong with this code ? (140 lines)
       From: Lustig, Roger <roger.lustig@CITIGROUP.COM>
     • Re: What is wrong with this code ? (158 lines)
       From: Terjeson, Mark <TERJEM@DSHS.WA.GOV>
     • Re: What is wrong with this code ? (165 lines)
       From: Nat Wooding <Nathaniel_Wooding@DOM.COM>

162. What the heck is UPPER()?
     • What the heck is UPPER()? (78 lines)
       From: Pardee, Roy <pardee.r@GHC.ORG>
     • Re: What the heck is UPPER()? (136 lines)
       From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
     • Re: What the heck is UPPER()? (104 lines)
       From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
     • Re: What the heck is UPPER()? (18 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: What the heck is UPPER()? (125 lines)
       From: Don & Susann <don_stanley@PARADISE.NET.NZ>
     • Re: What the heck is UPPER()? (144 lines)
       From: Pardee, Roy <pardee.r@GHC.ORG>
     • Re: What the heck is UPPER()? (142 lines)
       From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
     • Re: What the heck is UPPER()? (158 lines)
       From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
     • Re: What the heck is UPPER()? (219 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: What the heck is UPPER()? (155 lines)
       From: Pardee, Roy <pardee.r@GHC.ORG>
     • Re: What the heck is UPPER()? (208 lines)
       From: Pardee, Roy <pardee.r@GHC.ORG>
     • Re: What the heck is UPPER()? (237 lines)
       From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>
     • Re: What the heck is UPPER()? (229 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: What the heck is UPPER()? (241 lines)
       From: Pardee, Roy <pardee.r@GHC.ORG>
     • Re: What the heck is UPPER()? (229 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: What the heck is UPPER()? (189 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
     • Re: What the heck is UPPER()? (167 lines)
       From: Don & Susann <don_stanley@PARADISE.NET.NZ>

163. What's the best solution to do many to many merge? Thanks!
     • What's the best solution to do many to many merge? Thanks! (50 lines)
       From: SAS L <sasluser@YAHOO.COM>
     • Re: What's the best solution to do many to many merge? Thanks! (155 lines)
       From: Terjeson, Mark <TERJEM@DSHS.WA.GOV>
     • Re: What's the best solution to do many to many merge? Thanks! (122 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: What's the best solution to do many to many merge? Thanks! (91 lines)
       From: Paul M. Dorfman <sashole@BELLSOUTH.NET>
     • Re: What's the best solution to do many to many merge? Thanks! (185 lines)
       From: SAS L <sasluser@YAHOO.COM>
     • Re: What's the best solution to do many to many merge? Thanks! (253 lines)
       From: SAS L <sasluser@YAHOO.COM>
     • Re: What's the best solution to do many to many merge? Thanks! (290 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: What's the best solution to do many to many merge? Thanks! (212 lines)
       From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

164. What's the best solution to do many to many merge?Thanks!
     • Re: What's the best solution to do many to many merge?Thanks! (64 lines)
       From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM>

165. When a merge fails but SQL does not - 'Merge GotCha'
     • Re: When a merge fails but SQL does not - 'Merge GotCha' (172 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>

166. White Heteroskedasticity - ACOV
     • White Heteroskedasticity - ACOV (17 lines)
       From: Thomas <tythong@YAHOO.COM>
     • Re: White Heteroskedasticity - ACOV (106 lines)
       From: Nathan Fong <nmfong@HOTMAIL.COM>
     • Re: White Heteroskedasticity - ACOV (47 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

167. Winsorization
     • Winsorization (21 lines)
       From: Microstructure <randistan69@HOTMAIL.COM>
     • Re: Winsorization (90 lines)
       From: Pardee, Roy <pardee.r@GHC.ORG>
     • Re: Winsorization (57 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
     • Re: Winsorization (47 lines)
       From: Peter Flom <flom@NDRI.ORG>

168. YOU HAVE WON A LOTTO
     • YOU HAVE WON A LOTTO (98 lines)
       From: losun2@TISCALI.CO.UK

169. YOUR LOTTERY AWARD WINNING NOTIFCATION
     • YOUR LOTTERY AWARD WINNING NOTIFCATION (57 lines)
       From: blsp <blsp@TELSTRA.COM>

170. Your lotto Winning acknowledgement Note
     • Your lotto Winning acknowledgement Note (124 lines)
       From: Undetermined origin c/o LISTSERV administrator <owner-LISTSERV@AKH-WIEN.AC.AT>

171. ZIP for dummies
     • ZIP for dummies (33 lines)
       From: Jeffrey Stratford <stratja@AUBURN.EDU>

172. arrangements of indistinguishable objects?
     • arrangements of indistinguishable objects? (22 lines)
       From: K*F <kafernan@UWATERLOO.CA>
     • Re: arrangements of indistinguishable objects? (33 lines)
       From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
     • Re: arrangements of indistinguishable objects? (60 lines)
       From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
     • Re: arrangements of indistinguishable objects? (67 lines)
       From: Dunn, Toby <tdunn@TEA.STATE.TX.US>

173. arrows
     • arrows (34 lines)
       From: Carlos Tadeu Santos Dias <ctsdias@CARPA.CIAGRI.USP.BR>
     • Re: arrows (61 lines)
       From: Huang, Ya <yhuang@AMYLIN.COM>
     • Re: arrows (53 lines)
       From: Huang, Ya <yhuang@AMYLIN.COM>

174. attn: Stop to risk your life. alleles
     • attn: Stop to risk your life. alleles (64 lines)
       From: Sealarke <nataly21Vivian@EPIQMAIL.COM>

175. attn: Stop to risk your life. roster
     • attn: Stop to risk your life. roster (23 lines)
       From: Sit <bestsoftwarestringers@DCEMAIL.COM>

176. automatically delete the file and Over write on it
     • automatically delete the file and Over write on it (40 lines)
       From: kumar <subramanyam_22@YAHOO.COM>
     • Re: automatically delete the file and Over write on it (63 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

177. clearing macro variable from memory
     • clearing macro variable from memory (32 lines)
       From: Jamil Ibrahim <jibrahim@IR.UMSMED.EDU>
     • Re: clearing macro variable from memory (53 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: clearing macro variable from memory (46 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: clearing macro variable from memory (95 lines)
       From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
     • Re: clearing macro variable from memory (66 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

178. coding problem
     • coding problem (27 lines)
       From: rohitwmu <rohitwmu@INDIATIMES.COM>
     • Re: coding problem (63 lines)
       From: baogong jiang <bgjiang@GMAIL.COM>
     • Re: coding problem (68 lines)
       From: Paul M. Dorfman <sashole@BELLSOUTH.NET>

179. comparing two groups' mean
     • comparing two groups' mean (30 lines)
       From: Uekawa, Kazuaki <KUekawa@AIR.ORG>
     • Re: comparing two groups' mean (50 lines)
       From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU>
     • Re: comparing two groups' mean (63 lines)
       From: Peter Flom <flom@NDRI.ORG>
     • Re: comparing two groups' mean (80 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

180. counter for percent agreement
     • counter for percent agreement (17 lines)
       From: John A. Hansen <joahanse@INDIANA.EDU>
     • Re: counter for percent agreement (66 lines)
       From: Paul M. Dorfman <sashole@BELLSOUTH.NET>
     • Re: counter for percent agreement (74 lines)
       From: Chang Y. Chung <chang_y_chung@HOTMAIL.COM>
     • Re: counter for percent agreement (48 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

181. creating sequential id
     • Re: creating sequential id (158 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: creating sequential id (141 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>
     • Re: creating sequential id (172 lines)
       From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>

182. debrief: SAS Breakthru Tour
     • debrief: SAS Breakthru Tour (116 lines)
       From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>
     • Re: debrief: SAS Breakthru Tour (27 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
     • Re: debrief: SAS Breakthru Tour (19 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: debrief: SAS Breakthru Tour (35 lines)
       From: Dianne Rhodes <RHODESD1@WESTAT.COM>
     • Re: debrief: SAS Breakthru Tour (127 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: debrief: SAS Breakthru Tour (38 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
     • Re: debrief: SAS Breakthru Tour (44 lines)
       From: Fehd, Ronald J. (PHPPO) <RJF2@CDC.GOV>

183. dfbetas
     • Re: dfbetas (32 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

184. enIarge your p-e-n-l-s anything kilohm
     • enIarge your p-e-n-l-s anything kilohm (70 lines)
       From: Allan <TedNoservictors@WHOEVER.COM>

185. enterprise guide and XP login
     • enterprise guide and XP login (30 lines)
       From: dg <queanbeyan@HOTMAIL.COM>
     • Re: enterprise guide and XP login (58 lines)
       From: Alan Churchill <EmailMeDirectly@THISWEBSITE-ERRATIX.US>

186. gS_gE_gX adventures! regulators beefing
     • gS_gE_gX adventures! regulators beefing (68 lines)
       From: Andreas <TirreRozedishes@CLIFFHANGER.COM>

187. hope to hear from you
     • hope to hear from you (71 lines)
       From: frank247@POST.CZ

188. how do you display Proc Summary timedata ?
     • how do you display Proc Summary timedata ? (19 lines)
       From: Nina Harris <sas@MAILINATOR.COM>
     • Re: how do you display Proc Summary timedata ? (39 lines)
       From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV>

189. how to increase width of formats for some characters variables?
     • how to increase width of formats for some characters variables? (38 lines)
       From: Brian K. Bouvier <bbouvier@FFIC.COM>
     • Re: how to increase width of formats for some characters variables? (54 lines)
       From: Pardee, Roy <pardee.r@GHC.ORG>
     • Re: how to increase width of formats for some characters variables? (94 lines)
       From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
     • Re: how to increase width of formats for some characters variables? (86 lines)
       From: Lou <lpogodajr292185@COMCAST.NET>

190. kappa
     • Re: kappa (27 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
     • Re: kappa (45 lines)
       From: John Uebersax <jsuebersax@YAHOO.COM>

191. load SAS table into DB2 temporary table
     • load SAS table into DB2 temporary table (189 lines)
       From: tonts <tonts@CLUB-INTERNET.FR>

192. long string -> hex -> decimal
     • long string -> hex -> decimal (46 lines)
       From: Bart Heinsius <eombah@HOTMAIL.COM>
     • Re: long string -> hex -> decimal (79 lines)
       From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
     • Re: long string -> hex -> decimal (144 lines)
       From: Choate, Paul@DDS <pchoate@DDS.CA.GOV>
     • Re: long string -> hex -> decimal (97 lines)
       From: Huang, Ya <yhuang@AMYLIN.COM>
     • Re: long string -> hex -> decimal (49 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
     • Re: long string -> hex -> decimal (52 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

193. macro variable holding more than one value - problem defined clearly
     • Re: macro variable holding more than one value - problem defined clearly (33 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

194. macros
     • Re: macros (49 lines)
       From: Christian Lensbjerg <christian.lensbjerg@ALMBRAND.DK>

195. newbie question
     • newbie question (25 lines)
       From: Brien Alkire <brien@RAND.ORG>
     • Re: newbie question (47 lines)
       From: Dunn, Toby <tdunn@TEA.STATE.TX.US>
     • Re: newbie question (60 lines)
       From: Uekawa, Kazuaki <KUekawa@AIR.ORG>
     • Re: newbie question (18 lines)
       From: Steve Raimi <steven.raimi@GM.COM>

196. passing in parameters to macro (newbie question)
     • passing in parameters to macro (newbie question) (47 lines)
       From: K*F <kafernan@UWATERLOO.CA>
     • Re: passing in parameters to macro (newbie question) (56 lines)
       From: K*F <kafernan@UWATERLOO.CA>
     • Re: passing in parameters to macro (newbie question) (32 lines)
       From: Nina Harris <sas@MAILINATOR.COM>
     • Re: passing in parameters to macro (newbie question) (75 lines)
       From: Jim Groeneveld <jim.groeneveld@VITATRON.COM>
     • Re: passing in parameters to macro (newbie question) (72 lines)
       From: Jim Groeneveld <jim.groeneveld@VITATRON.COM>
     • Re: passing in parameters to macro (newbie question) (87 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>
     • Re: passing in parameters to macro (newbie question) (22 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

197. phreg and var1*var2 (interaction variables)
     • phreg and var1*var2 (interaction variables) (24 lines)
       From: Erik Christiansen <ec@SELVMORDSFORSKNING.DK>
     • Re: phreg and var1*var2 (interaction variables) (65 lines)
       From: DePuy, Venita <depuy001@DCRI.DUKE.EDU>
     • Re: phreg and var1*var2 (interaction variables) (68 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

198. problem solved
     • problem solved (12 lines)
       From: Brien Alkire <brien@RAND.ORG>

199. proc spl question
     • proc spl question (71 lines)
       From: helen <chenghelen2000@YAHOO.COM>
     • Re: proc spl question (125 lines)
       From: Dunn, Toby <tdunn@TEA.STATE.TX.US>

200. question on format of datetime hours
     • question on format of datetime hours (23 lines)
       From: Nina Harris <sas@MAILINATOR.COM>
     • Re: question on format of datetime hours (25 lines)
       From: mikko heikkinen <mh@EXTREMETECH.COM>

201. read a large flat file
     • Re: read a large flat file (93 lines)
       From: SUBSCRIBE SAS-L Stephane <datametric@CLUB-INTERNET.FR>
     • Re: read a large flat file (79 lines)
       From: SUBSCRIBE SAS-L Stephane <datametric@CLUB-INTERNET.FR>
     • Re: read a large flat file (102 lines)
       From: SUBSCRIBE SAS-L Stephane <datametric@CLUB-INTERNET.FR>
     • Re: read a large flat file (47 lines)
       From: Richard A. DeVenezia <radevenz@IX.NETCOM.COM>
     • Re: read a large flat file (141 lines)
       From: Peter Crawford <peter.crawford@BLUEYONDER.CO.UK>
     • Re: read a large flat file (157 lines)
       From: SUBSCRIBE SAS-L Stephane <datametric@CLUB-INTERNET.FR>
     • Re: read a large flat file (45 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

202. repeated measures, correlation between parities
     • repeated measures, correlation between parities (25 lines)
       From: rider_tiger <palacop@HOTMAIL.COM>

203. reply pls!!!
     • reply pls!!! (28 lines)
       From: MRS. MARIAM ABACHA. <mariamabacha@YAHOO.COM>

204. residuals in regression analysis
     • Re: residuals in regression analysis (44 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

205. sas menu
     • Re: sas menu (116 lines)
       From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>

206. starting excel and decimal point
     • starting excel and decimal point (47 lines)
       From: tonts <tonts@CLUB-INTERNET.FR>
     • Re: starting excel and decimal point (22 lines)
       From: tonts <tonts@CLUB-INTERNET.FR>

207. sur in syslin
     • sur in syslin (13 lines)
       From: P.-Guillaume M?on <pierre-guillaume.meon@URS.U-STRASBG.FR>
     • Re: sur in syslin (33 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

208. this offer is yours
     • this offer is yours (41 lines)
       From: ahmedalla0330 <ahmedalla0330@TELSTRA.COM>

209. unequal spacing, Proc MIXED
     • unequal spacing, Proc MIXED (45 lines)
       From: Lars Pettersson <larsp1@IDGMAIL.SE>
     • Re: unequal spacing, Proc MIXED (174 lines)
       From: Dale McLerran <stringplayer_2@YAHOO.COM>

210. value with an ampersand
     • value with an ampersand (28 lines)
       From: statistics <conjecture@GEOCITIES.COM>
     • Re: value with an ampersand (48 lines)
       From: Guido <cymraeg_erict@HOTMAIL.COM>
     • Re: value with an ampersand (77 lines)
       From: Groeneveld, Jim <jim.groeneveld@VITATRON.COM>
     • Re: value with an ampersand (40 lines)
       From: christopher <chris.chan@WEBMININGPRO.COM>
     • Re: value with an ampersand (74 lines)
       From: Jim Groeneveld <jim.groeneveld@VITATRON.COM>
     • Re: value with an ampersand (63 lines)
       From: David L. Cassell <cassell.david@EPAMAIL.EPA.GOV>

211. x0pjb
     • x0pjb (5660 lines)
       From: . <all_a@INBOX.RU>