Table of contents:

• "Row title space too small to print titles for the table statement" error (3 messages)
• "Unpacking" variable in a datastep into a "macro function" (14 messages)
• A bootstrapping/simulation question
• Animal Shelters & Survey Statisticians
• Annual meetup (BOF) -- save the date and time! (5 messages)
• Audit trails (3 messages)
• Automatic reply: SAS-L Digest - 11 Mar 2011 - Special issue (#2011-301)
• Automatic reply: SAS-L Digest - 11 Mar 2011 - Special issue (#2011-303)
• Automatic reply: Web reading macro
• Call to execute SQL commands within SAS? (5 messages)
• Can someone using 9.2 64-bit Windows test this? (2 messages)
• Chance to Make SAS-L History: Did You Know That... (4 messages)
• Checking for whitespace (8 messages)
• Circular dot plot (10 messages)
• Conditional Execution of Parameter in EG QUERY BUILDER
• Documentation for AMO 4.3 Input Streams?
• ERROR: Index TEMPINDX cannot be created
• Error Msg with Tagsets ExcelXP (4 messages)
• Estimating Difference in Centroids in Multivariate Linear Mixed Model (2 messages)
• Excel Formulas and ODBC (2 messages)
• FORECAST-- help (2 messages)
• Find Different Names (6 messages)
• Fuzzy pattern matching
• Gap Determination (3 messages)
• Green on PROC GCHART and SAS graphics (2 messages)
• How can I replace the characters by a list in a fast way (13 messages)
• How to convert date format (7 messages)
• How to get the data set id when the data set has been openned? (2 messages)
• How to solve this senario? (2 messages)
• JOBS (4 messages)
• Launching stored processes in code or in another stored process (5 messages)
• Learning Edition and Enterprise Miner (6 messages)
• MANOVA
• Named setting
• Number of decimals (3 messages)
• ODS (2 messages)
• OT: Cute Comp Sci Joke
• OT: Friday Humor (11 messages)
• OT: Is this interview question misleading? (4 messages)
• OT: using SQL with MS Access (4 messages)
• Outputting to PDF / "save as" dialog box popping up every time for 200x loop (4 messages)
• PROC RANK Percentiles vs. PROC UNIVARIATE Percentiles (5 messages)
• PROC UNIVARIATE: suppress output (4 messages)
• Payment agreement coding (2 messages)
• PhilaSUG Spring 2011 Meeting Call For Paper and Poster Presentations
• Proc Format Woes (3 messages)
• Proc GMAP coloring (4 messages)
• Proc Sql Update with 2 Tables (6 messages)
• Proc means completetypes and Proc SQL
• Quotation Marks in SAS Macro (3 messages)
• REMINDER: NJ SAS Users Group Meeting - Friday, March 25th at Rutgers University
• RES: FORECAST-- help
• Reading data from a website (3 messages)
• Reference cell coding and regression (2 messages)
• Referencing SAS in a publication (4 messages)
• Relative path names in view
• SAS Datetime Variable Conversionm XXXX (4 messages)
• SAS Speakers Confirmed; Early Reg. Offer Ends Soon (3 messages)
• SAS+Access v.s. VBA+SQL+Access (4 messages)
• SASware ballot
• SCALABLE way to find all-null columns? (8 messages)
• SQL lookup - more efficient way? (5 messages)
• SYSRC vs MODULEN
• Scanning a character string for a number XXXX (3 messages)
• Two of our members are famous (3 messages)
• Unbalanced files (2 messages)
• Using Qutation Marks in SAS (2 messages)
• Web reading macro (3 messages)
• Weighted historgams and boxplots (3 messages)
• conditional highlighting in reports (2 messages)
• data prep
• excelxp tagsets = extremely bloated files (3 messages)
• firstobs vs. input # (5 messages)
• how do you generate a random .. (2 messages)
• how to retrieve the SAS outputs stored in a catalog (6 messages)
• install SAS 64-bit on Win 7 issue: JAVA JRE (6 messages)
• problems importing datetimes from csv files (18 messages)
• proc SQL and Length (8 messages)
• prxmatch called within a macro - escaping special characters (3 messages)
• remove a single space from a string (5 messages)
• remove a single space from a string - solved - use compress
• replacing var name with label in multiway list format
• reshuffle and pick data (11 messages)
• sybase connection error
• using SAS PROC SQL to manipulate databases (2 messages)

1. "Row title space too small to print titles for the table statement" error
   • "Row title space too small to print titles for the table statement" error (68 lines)
     From: White, Svend A. <SvendW@HEALTH.OK.GOV>
   • Re: "Row title space too small to print titles for the table statement" error (73 lines)
     From: Data _null_; <iebupdte@GMAIL.COM>
   • Re: "Row title space too small to print titles for the table statement" error (93 lines)
     From: White, Svend A. <SvendW@HEALTH.OK.GOV>

2. "Unpacking" variable in a datastep into a "macro function"
   • "Unpacking" variable in a datastep into a "macro function" (34 lines)
     From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV>
   • Re: "Unpacking" variable in a datastep into a "macro function" (48 lines)
     From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
   • Re: "Unpacking" variable in a datastep into a "macro function" (70 lines)
     From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
   • Re: "Unpacking" variable in a datastep into a "macro function" (103 lines)
     From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV>
   • Re: "Unpacking" variable in a datastep into a "macro function" (114 lines)
     From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
   • Re: "Unpacking" variable in a datastep into a "macro function" (126 lines)
     From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV>
   • Re: "Unpacking" variable in a datastep into a "macro function" (37 lines)
     From: Chang Chung <chang_y_chung@HOTMAIL.COM>
   • Re: "Unpacking" variable in a datastep into a "macro function" (21 lines)
     From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV>
   • Re: "Unpacking" variable in a datastep into a "macro function" (140 lines)
     From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
   • Re: "Unpacking" variable in a datastep into a "macro function" (230 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: "Unpacking" variable in a datastep into a "macro function" (93 lines)
     From: Sprague, Webb (OFM) <Webb.Sprague@OFM.WA.GOV>
   • Re: "Unpacking" variable in a datastep into a "macro function" (193 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: "Unpacking" variable in a datastep into a "macro function" (115 lines)
     From: Tom Abernathy <tom.abernathy@GMAIL.COM>
   • Re: "Unpacking" variable in a datastep into a "macro function" (43 lines)
     From: Ben Herman <baherman@GMAIL.COM>

3. A bootstrapping/simulation question
   • A bootstrapping/simulation question (58 lines)
     From: Paul Miller <pjmiller_57@YAHOO.COM>

4. Animal Shelters & Survey Statisticians
   • Animal Shelters & Survey Statisticians (53 lines)
     From: Gina Clemmer <gclemmer@URBAN-RESEARCH.INFO>

5. Annual meetup (BOF) -- save the date and time!
   • Annual meetup (BOF) -- save the date and time! (38 lines)
     From: Mike Rhoads <RHOADSM1@WESTAT.COM>
   • Re: Annual meetup (BOF) -- save the date and time! (66 lines)
     From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
   • Re: Annual meetup (BOF) -- save the date and time! (71 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>
   • Re: Annual meetup (BOF) -- save the date and time! (86 lines)
     From: Mike Rhoads <RHOADSM1@WESTAT.COM>
   • Re: Annual meetup (BOF) -- save the date and time! (44 lines)
     From: Michael Raithel <michaelraithel@WESTAT.COM>

6. Audit trails
   • Audit trails (20 lines)
     From: Sterling Paramore <gnilrets@GMAIL.COM>
   • Re: Audit trails (46 lines)
     From: toby dunn <tobydunn@HOTMAIL.COM>
   • Re: Audit trails (60 lines)
     From: Sterling Paramore <gnilrets@GMAIL.COM>

7. Automatic reply: SAS-L Digest - 11 Mar 2011 - Special issue (#2011-301)
   • Automatic reply: SAS-L Digest - 11 Mar 2011 - Special issue (#2011-301) (14 lines)
     From: Carol Olson <Carol.Olson@MEREDITH.COM>

8. Automatic reply: SAS-L Digest - 11 Mar 2011 - Special issue (#2011-303)
   • Automatic reply: SAS-L Digest - 11 Mar 2011 - Special issue (#2011-303) (16 lines)
     From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU>

9. Automatic reply: Web reading macro
   • Automatic reply: Web reading macro (13 lines)
     From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

10. Call to execute SQL commands within SAS?
    • Call to execute SQL commands within SAS? (54 lines)
      From: Bian, Haikuo <HBian@NW7.ESRD.NET>
    • Re: Call to execute SQL commands within SAS? (49 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Call to execute SQL commands within SAS? (59 lines)
      From: Bian, Haikuo <HBian@NW7.ESRD.NET>
    • Re: Call to execute SQL commands within SAS? (92 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Call to execute SQL commands within SAS? (69 lines)
      From: Bian, Haikuo <HBian@NW7.ESRD.NET>

11. Can someone using 9.2 64-bit Windows test this?
    • Re: Can someone using 9.2 64-bit Windows test this? (87 lines)
      From: Ben Herman <baherman@GMAIL.COM>
    • Re: Can someone using 9.2 64-bit Windows test this? (31 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

12. Chance to Make SAS-L History: Did You Know That...
    • Re: Chance to Make SAS-L History: Did You Know That... (85 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Chance to Make SAS-L History: Did You Know That... (78 lines)
      From: Clark An <kuhasu@126.COM>
    • Re: Chance to Make SAS-L History: Did You Know That... (110 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Chance to Make SAS-L History: Did You Know That... (119 lines)
      From: Clark An <kuhasu@126.COM>

13. Checking for whitespace
    • Checking for whitespace (40 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Checking for whitespace (51 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Checking for whitespace (66 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Checking for whitespace (77 lines)
      From: Robin R High <rhigh@UNMC.EDU>
    • Re: Checking for whitespace (102 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Checking for whitespace (150 lines)
      From: Ben Herman <baherman@GMAIL.COM>
    • Re: Checking for whitespace (164 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Checking for whitespace (182 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

14. Circular dot plot
    • Circular dot plot (33 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Circular dot plot (52 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Circular dot plot (51 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Circular dot plot (69 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Circular dot plot (72 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>
    • Re: Circular dot plot (90 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Circular dot plot (90 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Circular dot plot (96 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>
    • Re: Circular dot plot (116 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Circular dot plot (144 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

15. Conditional Execution of Parameter in EG QUERY BUILDER
    • Conditional Execution of Parameter in EG QUERY BUILDER (40 lines)
      From: John RR <john_rr_irc@YAHOO.COM>

16. Documentation for AMO 4.3 Input Streams?
    • Documentation for AMO 4.3 Input Streams? (16 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>

17. ERROR: Index TEMPINDX cannot be created
    • Re: ERROR: Index TEMPINDX cannot be created (71 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

18. Error Msg with Tagsets ExcelXP
    • Error Msg with Tagsets ExcelXP (108 lines)
      From: Kim Brown <kibrown@LADHS.ORG>
    • Re: Error Msg with Tagsets ExcelXP (11 lines)
      From: Kim Brown <kibrown@LADHS.ORG>
    • Re: Error Msg with Tagsets ExcelXP (50 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: Error Msg with Tagsets ExcelXP (7 lines)
      From: Kim Brown <kibrown@LADHS.ORG>

19. Estimating Difference in Centroids in Multivariate Linear Mixed Model
    • Estimating Difference in Centroids in Multivariate Linear Mixed Model (59 lines)
      From: R B <ryan.andrew.black@GMAIL.COM>
    • Re: Estimating Difference in Centroids in Multivariate Linear Mixed Model (86 lines)
      From: R B <ryan.andrew.black@GMAIL.COM>

20. Excel Formulas and ODBC
    • Excel Formulas and ODBC (100 lines)
      From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM>
    • Re: Excel Formulas and ODBC (123 lines)
      From: John Birken <zbq5@CDC.GOV>

21. FORECAST-- help
    • Re: FORECAST-- help (18 lines)
      From: Pradeep <chittiprolupradeep@GMAIL.COM>
    • Re: FORECAST-- help (49 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

22. Find Different Names
    • Find Different Names (39 lines)
      From: Wei Wang <weiwangum@YAHOO.COM>
    • Re: Find Different Names (62 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Find Different Names (83 lines)
      From: Wei Wang <weiwangum@YAHOO.COM>
    • Re: Find Different Names (106 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>
    • Re: Find Different Names (105 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Find Different Names (79 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

23. Fuzzy pattern matching
    • Re: Fuzzy pattern matching (60 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>

24. Gap Determination
    • Re: Gap Determination (149 lines)
      From: Dave Brewer <david.brewer@UC.EDU>
    • Re: Gap Determination (195 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: Gap Determination (208 lines)
      From: Dave <david.brewer@UC.EDU>

25. Green on PROC GCHART and SAS graphics
    • Green on PROC GCHART and SAS graphics (73 lines)
      From: Long, Stuart (NIH/NIEHS) [C] <long3@NIEHS.NIH.GOV>
    • Re: Green on PROC GCHART and SAS graphics (79 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>

26. How can I replace the characters by a list in a fast way
    • How can I replace the characters by a list in a fast way (15 lines)
      From: Clark An <kuhasu@126.COM>
    • Re: How can I replace the characters by a list in a fast way (10 lines)
      From: Clark An <kuhasu@126.COM>
    • Re: How can I replace the characters by a list in a fast way (64 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: How can I replace the characters by a list in a fast way (71 lines)
      From: Clark An <kuhasu@126.COM>
    • Re: How can I replace the characters by a list in a fast way (110 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: How can I replace the characters by a list in a fast way (84 lines)
      From: Clark An <kuhasu@126.COM>
    • Re: How can I replace the characters by a list in a fast way (131 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: How can I replace the characters by a list in a fast way (97 lines)
      From: Clark An <kuhasu@126.COM>
    • Re: How can I replace the characters by a list in a fast way (100 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: How can I replace the characters by a list in a fast way (113 lines)
      From: Clark An <kuhasu@126.COM>
    • Re: How can I replace the characters by a list in a fast way (124 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: How can I replace the characters by a list in a fast way (145 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: How can I replace the characters by a list in a fast way (131 lines)
      From: Clark An <kuhasu@126.COM>

27. How to convert date format
    • How to convert date format (15 lines)
      From: jn mao <jn_mao@YAHOO.COM>
    • Re: How to convert date format (39 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: How to convert date format (50 lines)
      From: jn mao <jn_mao@YAHOO.COM>
    • Re: How to convert date format (58 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: How to convert date format (66 lines)
      From: jn mao <jn_mao@YAHOO.COM>
    • Re: How to convert date format (98 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: How to convert date format (109 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

28. How to get the data set id when the data set has been openned?
    • Re: How to get the data set id when the data set has been openned? (29 lines)
      From: Clark An <kuhasu@126.COM>
    • Re: How to get the data set id when the data set has been openned? (68 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

29. How to solve this senario?
    • How to solve this senario? (59 lines)
      From: Shaik Hymad <hymadsk@GMAIL.COM>
    • Re: How to solve this senario? (79 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>

30. JOBS
    • JOBS (18 lines)
      From: Sandya Sangam <sandya.sangam@GOOGLEMAIL.COM>
    • Re: JOBS (43 lines)
      From: Núria Chapinal <nchapinal@YAHOO.COM>
    • Re: JOBS (40 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: JOBS (34 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

31. Launching stored processes in code or in another stored process
    • Launching stored processes in code or in another stored process (18 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Launching stored processes in code or in another stored process (39 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Launching stored processes in code or in another stored process (56 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Launching stored processes in code or in another stored process (45 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: Launching stored processes in code or in another stored process (88 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

32. Learning Edition and Enterprise Miner
    • Learning Edition and Enterprise Miner (27 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Learning Edition and Enterprise Miner (48 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Learning Edition and Enterprise Miner (53 lines)
      From: boy cynic <goodmood.cynic8@GMAIL.COM>
    • Re: Learning Edition and Enterprise Miner (67 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: Learning Edition and Enterprise Miner (74 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Learning Edition and Enterprise Miner (34 lines)
      From: T J <tj_noreply@YAHOO.COM>

33. MANOVA
    • MANOVA (33 lines)
      From: William Shakespeare <shakespeare_1040@HOTMAIL.COM>

34. Named setting
    • Named setting (17 lines)
      From: Masoud Pajoh <mpajoh@ODOT.ORG>

35. Number of decimals
    • Number of decimals (15 lines)
      From: Ali Zanaty <zanaty2005@YAHOO.COM>
    • Re: Number of decimals (26 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Number of decimals (33 lines)
      From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV>

36. ODS
    • Re: ODS (47 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: ODS (73 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

37. OT: Cute Comp Sci Joke
    • OT: Cute Comp Sci Joke (26 lines)
      From: Alan Churchill <alan.churchill@SAVIAN.NET>

38. OT: Friday Humor
    • OT: Friday Humor (16 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: OT: Friday Humor (38 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: OT: Friday Humor (36 lines)
      From: F J Kelley <jkelley@UGA.EDU>
    • Re: OT: Friday Humor (44 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: OT: Friday Humor (58 lines)
      From: F J Kelley <jkelley@UGA.EDU>
    • Re: OT: Friday Humor (32 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: OT: Friday Humor (38 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: OT: Friday Humor (50 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: OT: Friday Humor (96 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: OT: Friday Humor (101 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: OT: Friday Humor (119 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

39. OT: Is this interview question misleading?
    • OT: Is this interview question misleading? (49 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: OT: Is this interview question misleading? (73 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: OT: Is this interview question misleading? (110 lines)
      From: Reeza K <fkhurshed@HOTMAIL.COM>
    • Re: OT: Is this interview question misleading? (124 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>

40. OT: using SQL with MS Access
    • OT: using SQL with MS Access (23 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: OT: using SQL with MS Access (30 lines)
      From: Ben Herman <baherman@GMAIL.COM>
    • Re: OT: using SQL with MS Access (56 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: OT: using SQL with MS Access (40 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

41. Outputting to PDF / "save as" dialog box popping up every time for 200x loop
    • Outputting to PDF / "save as" dialog box popping up every time for 200x loop (31 lines)
      From: CO_SAS_Guy <jason.gannon@YAHOO.COM>
    • Re: Outputting to PDF / "save as" dialog box popping up every time for 200x loop (40 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Outputting to PDF / "save as" dialog box popping up every time for 200x loop (47 lines)
      From: Susan Durham <sdurham@BIOLOGY.USU.EDU>
    • Re: Outputting to PDF / "save as" dialog box popping up every time for 200x loop (9 lines)
      From: CO_SAS_guy <jason.gannon@YAHOO.COM>

42. PROC RANK Percentiles vs. PROC UNIVARIATE Percentiles
    • PROC RANK Percentiles vs. PROC UNIVARIATE Percentiles (99 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: PROC RANK Percentiles vs. PROC UNIVARIATE Percentiles (115 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: PROC RANK Percentiles vs. PROC UNIVARIATE Percentiles (185 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: PROC RANK Percentiles vs. PROC UNIVARIATE Percentiles (146 lines)
      From: Schaan, Desiree <Desiree.Schaan@OCC.TREAS.GOV>
    • Re: PROC RANK Percentiles vs. PROC UNIVARIATE Percentiles (157 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>

43. PROC UNIVARIATE: suppress output
    • PROC UNIVARIATE: suppress output (20 lines)
      From: Long, Stuart (NIH/NIEHS) [C] <long3@NIEHS.NIH.GOV>
    • Re: PROC UNIVARIATE: suppress output (39 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: PROC UNIVARIATE: suppress output (32 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: PROC UNIVARIATE: suppress output (57 lines)
      From: Long, Stuart (NIH/NIEHS) [C] <long3@NIEHS.NIH.GOV>

44. Payment agreement coding
    • Payment agreement coding (168 lines)
      From: Yingtao <yingtaoliu@GMAIL.COM>
    • Re: Payment agreement coding (182 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>

45. PhilaSUG Spring 2011 Meeting Call For Paper and Poster Presentations
    • PhilaSUG Spring 2011 Meeting Call For Paper and Poster Presentations (60 lines)
      From: Robert Schechter <robert.schechter@COMCAST.NET>

46. Proc Format Woes
    • Proc Format Woes (46 lines)
      From: Karl M. Fernstrom <kfernstrom@GMAIL.COM>
    • Re: Proc Format Woes (83 lines)
      From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>
    • Re: Proc Format Woes (95 lines)
      From: Karl M. Fernstrom <kfernstrom@GMAIL.COM>

47. Proc GMAP coloring
    • Proc GMAP coloring (203 lines)
      From: Adams, Nicholas <NRAdams@CVTY.COM>
    • Re: Proc GMAP coloring (212 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Proc GMAP coloring (233 lines)
      From: Adams, Nicholas <NRAdams@CVTY.COM>
    • Re: Proc GMAP coloring (223 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

48. Proc Sql Update with 2 Tables
    • Proc Sql Update with 2 Tables (28 lines)
      From: Eduardo Galvan <egalvan@ISR.UMICH.EDU>
    • Re: Proc Sql Update with 2 Tables (61 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Proc Sql Update with 2 Tables (121 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Proc Sql Update with 2 Tables (45 lines)
      From: Reeza K <fkhurshed@HOTMAIL.COM>
    • Re: Proc Sql Update with 2 Tables (125 lines)
      From: Eduardo Galvan <egalvan@ISR.UMICH.EDU>
    • Re: Proc Sql Update with 2 Tables (136 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

49. Proc means completetypes and Proc SQL
    • Proc means completetypes and Proc SQL (60 lines)
      From: SAS_learner <proccontents@GMAIL.COM>

50. Quotation Marks in SAS Macro
    • Quotation Marks in SAS Macro (45 lines)
      From: Student Statistics <student.statistics@GMAIL.COM>
    • Re: Quotation Marks in SAS Macro (78 lines)
      From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
    • Re: Quotation Marks in SAS Macro (58 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

51. REMINDER: NJ SAS Users Group Meeting - Friday, March 25th at Rutgers University
    • REMINDER: NJ SAS Users Group Meeting - Friday, March 25th at Rutgers University (32 lines)
      From: NJ SAS Users Group <nj.sas.users.group@GMAIL.COM>

52. RES: FORECAST-- help
    • RES: FORECAST-- help (35 lines)
      From: Ricardo Gonçalves da Silva <rgs.rsilva@BANCOVOTORANTIM.COM.BR>

53. Reading data from a website
    • Reading data from a website (17 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Reading data from a website (48 lines)
      From: Murphy Choy <goladin@GMAIL.COM>
    • Re: Reading data from a website (66 lines)
      From: Murphy Choy <goladin@GMAIL.COM>

54. Reference cell coding and regression
    • Reference cell coding and regression (17 lines)
      From: Pam Shin <pg2003sf@YAHOO.COM>
    • Re: Reference cell coding and regression (39 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

55. Referencing SAS in a publication
    • Referencing SAS in a publication (39 lines)
      From: Sudo Ku <crafty876@HOTMAIL.COM>
    • Re: Referencing SAS in a publication (47 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Referencing SAS in a publication (56 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Referencing SAS in a publication (66 lines)
      From: Sudo Ku <crafty876@HOTMAIL.COM>

56. Relative path names in view
    • Re: Relative path names in view (26 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>

57. SAS Datetime Variable Conversionm XXXX
    • SAS Datetime Variable Conversionm XXXX (23 lines)
      From: Dan Abner <dan.abner99@GMAIL.COM>
    • Re: SAS Datetime Variable Conversionm XXXX (34 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: SAS Datetime Variable Conversionm XXXX (46 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: SAS Datetime Variable Conversionm XXXX (61 lines)
      From: Dan Abner <dan.abner99@GMAIL.COM>

58. SAS Speakers Confirmed; Early Reg. Offer Ends Soon
    • SAS Speakers Confirmed; Early Reg. Offer Ends Soon (137 lines)
      From: Richard Read Allen <peakstat@WISPERTEL.NET>
    • Re: SAS Speakers Confirmed; Early Reg. Offer Ends Soon (117 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: SAS Speakers Confirmed; Early Reg. Offer Ends Soon (129 lines)
      From: Richard Read Allen <peakstat@WISPERTEL.NET>

59. SAS+Access v.s. VBA+SQL+Access
    • SAS+Access v.s. VBA+SQL+Access (51 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: SAS+Access v.s. VBA+SQL+Access (71 lines)
      From: Alan Churchill <alan.churchill@SAVIAN.NET>
    • Re: SAS+Access v.s. VBA+SQL+Access (89 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: SAS+Access v.s. VBA+SQL+Access (121 lines)
      From: Alan Churchill <alan.churchill@SAVIAN.NET>

60. SASware ballot
    • SASware ballot (23 lines)
      From: Peter Crawford <Peter.Crawford@BLUEYONDER.CO.UK>

61. SCALABLE way to find all-null columns?
    • SCALABLE way to find all-null columns? (28 lines)
      From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM>
    • Re: SCALABLE way to find all-null columns? (86 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: SCALABLE way to find all-null columns? (55 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: SCALABLE way to find all-null columns? (64 lines)
      From: Steven Raimi <sraimi@MARKETINGASSOCIATES.COM>
    • Re: SCALABLE way to find all-null columns? (102 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>
    • Re: SCALABLE way to find all-null columns? (177 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: SCALABLE way to find all-null columns? (190 lines)
      From: Mike Rhoads <RHOADSM1@WESTAT.COM>
    • Re: SCALABLE way to find all-null columns? (66 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

62. SQL lookup - more efficient way?
    • SQL lookup - more efficient way? (32 lines)
      From: Michael Murff <mysasbox@GMAIL.COM>
    • Re: SQL lookup - more efficient way? (55 lines)
      From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>
    • Re: SQL lookup - more efficient way? (48 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: SQL lookup - more efficient way? (114 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
    • Re: SQL lookup - more efficient way? (99 lines)
      From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>

63. SYSRC vs MODULEN
    • SYSRC vs MODULEN (29 lines)
      From: Dan S <DanS@21STCENTURYSOFTWARE.COM>

64. Scanning a character string for a number XXXX
    • Scanning a character string for a number XXXX (21 lines)
      From: Dan Abner <dan.abner99@GMAIL.COM>
    • Re: Scanning a character string for a number XXXX (30 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: Scanning a character string for a number XXXX (30 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

65. Two of our members are famous
    • Two of our members are famous (13 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Two of our members are famous (49 lines)
      From: Michael Raithel <michaelraithel@WESTAT.COM>
    • Re: Two of our members are famous (45 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

66. Unbalanced files
    • Unbalanced files (48 lines)
      From: Bill Behrens <mngorgeman@GMAIL.COM>
    • Re: Unbalanced files (88 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

67. Using Qutation Marks in SAS
    • Using Qutation Marks in SAS (45 lines)
      From: Student Statistics <student.statistics@GMAIL.COM>
    • Re: Using Qutation Marks in SAS (57 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>

68. Web reading macro
    • Re: Web reading macro (31 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: Web reading macro (61 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Web reading macro (196 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

69. Weighted historgams and boxplots
    • Weighted historgams and boxplots (44 lines)
      From: Long, Stuart (NIH/NIEHS) [C] <long3@NIEHS.NIH.GOV>
    • Re: Weighted historgams and boxplots (51 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Weighted historgams and boxplots (65 lines)
      From: Long, Stuart (NIH/NIEHS) [C] <long3@NIEHS.NIH.GOV>

70. conditional highlighting in reports
    • conditional highlighting in reports (35 lines)
      From: Hiten Patel <hpatel@GIVEGET.COM>
    • Re: conditional highlighting in reports (55 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

71. data prep
    • data prep (50 lines)
      From: Val Krem <valkrem@YAHOO.COM>

72. excelxp tagsets = extremely bloated files
    • excelxp tagsets = extremely bloated files (106 lines)
      From: Scott Bass <sas_l_739@YAHOO.COM.AU>
    • Re: excelxp tagsets = extremely bloated files (117 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: excelxp tagsets = extremely bloated files (132 lines)
      From: Alan Churchill <alan.churchill@SAVIAN.NET>

73. firstobs vs. input #
    • firstobs vs. input # (64 lines)
      From: Nuria Chapinal <nchapinal@YAHOO.COM>
    • Re: firstobs vs. input # (91 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: firstobs vs. input # (133 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: firstobs vs. input # (181 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: firstobs vs. input # (210 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

74. how do you generate a random ..
    • how do you generate a random .. (16 lines)
      From: stat <tano.tano.2008@GMAIL.COM>
    • Re: how do you generate a random .. (40 lines)
      From: Jordan, Lewis <Lewis.Jordan@WEYERHAEUSER.COM>

75. how to retrieve the SAS outputs stored in a catalog
    • how to retrieve the SAS outputs stored in a catalog (24 lines)
      From: Peng, Lily <Lily.Peng@PHARMA.COM>
    • Re: how to retrieve the SAS outputs stored in a catalog (43 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: how to retrieve the SAS outputs stored in a catalog (55 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: how to retrieve the SAS outputs stored in a catalog (71 lines)
      From: Peng, Lily <Lily.Peng@PHARMA.COM>
    • Re: how to retrieve the SAS outputs stored in a catalog (89 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: how to retrieve the SAS outputs stored in a catalog (101 lines)
      From: Peng, Lily <Lily.Peng@PHARMA.COM>

76. install SAS 64-bit on Win 7 issue: JAVA JRE
    • install SAS 64-bit on Win 7 issue: JAVA JRE (29 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: install SAS 64-bit on Win 7 issue: JAVA JRE (39 lines)
      From: F J Kelley <jkelley@UGA.EDU>
    • Re: install SAS 64-bit on Win 7 issue: JAVA JRE (68 lines)
      From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>
    • Re: install SAS 64-bit on Win 7 issue: JAVA JRE (76 lines)
      From: F J Kelley <jkelley@UGA.EDU>
    • Re: install SAS 64-bit on Win 7 issue: JAVA JRE (37 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: install SAS 64-bit on Win 7 issue: JAVA JRE (60 lines)
      From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>

77. problems importing datetimes from csv files
    • problems importing datetimes from csv files (37 lines)
      From: Nuria Chapinal <nchapinal@YAHOO.COM>
    • Re: problems importing datetimes from csv files (104 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: problems importing datetimes from csv files (131 lines)
      From: Núria Chapinal <nchapinal@YAHOO.COM>
    • Re: problems importing datetimes from csv files (146 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: problems importing datetimes from csv files (155 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: problems importing datetimes from csv files (158 lines)
      From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>
    • Re: problems importing datetimes from csv files (153 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: problems importing datetimes from csv files (179 lines)
      From: DUELL, BOB (ATTCINW) <BD9439@ATT.COM>
    • Re: problems importing datetimes from csv files (193 lines)
      From: Núria Chapinal <nchapinal@YAHOO.COM>
    • Re: problems importing datetimes from csv files (218 lines)
      From: Núria Chapinal <nchapinal@YAHOO.COM>
    • Re: problems importing datetimes from csv files (32 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: problems importing datetimes from csv files (259 lines)
      From: Núria Chapinal <nchapinal@YAHOO.COM>
    • Re: problems importing datetimes from csv files (48 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: problems importing datetimes from csv files (42 lines)
      From: Nuria Chapinal <nchapinal@YAHOO.COM>
    • Re: problems importing datetimes from csv files (72 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: problems importing datetimes from csv files (100 lines)
      From: Núria Chapinal <nchapinal@YAHOO.COM>
    • Re: problems importing datetimes from csv files (118 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: problems importing datetimes from csv files (78 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>

78. proc SQL and Length
    • proc SQL and Length (20 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: proc SQL and Length (24 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: proc SQL and Length (37 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: proc SQL and Length (37 lines)
      From: Huang, Ya <Ya.Huang@AMYLIN.COM>
    • Re: proc SQL and Length (106 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: proc SQL and Length (50 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>
    • Re: proc SQL and Length (76 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: proc SQL and Length (90 lines)
      From: Jack Hamilton <jfh@STANFORDALUMNI.ORG>

79. prxmatch called within a macro - escaping special characters
    • prxmatch called within a macro - escaping special characters (53 lines)
      From: Scott Bass <sas_l_739@YAHOO.COM.AU>
    • Re: prxmatch called within a macro - escaping special characters (67 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: prxmatch called within a macro - escaping special characters (75 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>

80. remove a single space from a string
    • remove a single space from a string (37 lines)
      From: Craig Stroup <craig.stroup@FCC.GOV>
    • Re: remove a single space from a string (47 lines)
      From: Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
    • Re: remove a single space from a string (50 lines)
      From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
    • Re: remove a single space from a string (86 lines)
      From: Vipin Tripathi <vipinisvipin@GMAIL.COM>
    • Re: remove a single space from a string (78 lines)
      From: Vipin Tripathi <vipinisvipin@GMAIL.COM>

81. remove a single space from a string - solved - use compress
    • Re: remove a single space from a string - solved - use compress (11 lines)
      From: Craig Stroup <craig.stroup@FCC.GOV>

82. replacing var name with label in multiway list format
    • Re: replacing var name with label in multiway list format (120 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>

83. reshuffle and pick data
    • reshuffle and pick data (24 lines)
      From: oslo <hokut1@YAHOO.COM>
    • Re: reshuffle and pick data (69 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: reshuffle and pick data (40 lines)
      From: oslo <hokut1@YAHOO.COM>
    • Re: reshuffle and pick data (101 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: reshuffle and pick data (102 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: reshuffle and pick data (60 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: reshuffle and pick data (65 lines)
      From: oslo <hokut1@YAHOO.COM>
    • Re: reshuffle and pick data (180 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: reshuffle and pick data (225 lines)
      From: Richard Tritz <richardtritz@ATT.NET>
    • Re: reshuffle and pick data (121 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>
    • Re: reshuffle and pick data (53 lines)
      From: oslo <hokut1@YAHOO.COM>

84. sybase connection error
    • sybase connection error (31 lines)
      From: Bin Zhu <bxz01@HEALTH.STATE.NY.US>

85. using SAS PROC SQL to manipulate databases
    • using SAS PROC SQL to manipulate databases (22 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: using SAS PROC SQL to manipulate databases (31 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>