Table of contents:

• 2 SAS Professionals Needed Immediately For Contract Work--Rates $100+/Hour
• 90 instances of SAS display manager (4 messages)
• Analytic job openings available in exciting new area within healthcare: Payment Innovation
• Automatic reply: How to change FONT in annotatation facility
• Automatic reply: SAS-L Digest - 14 May 2012 to 15 May 2012 (#2012-354) (2 messages)
• Automatic reply: SAS-L Digest - 17 May 2012 to 18 May 2012 (#2012-367)
• Automatic reply: SAS-L Digest - 18 May 2012 - Special issue (#2012-368)
• Automatic reply: insert blanks
• Bricolage Report: SQL Tricks
• Checking memory use by a SAS process
• DEFINE INFINITE LOOP (10 messages)
• Detecting the Windows date format (10 messages)
• Extract id's with multiple (7 messages)
• For each obs, find the variable that contains the min value (12 messages)
• Fw: DEFINE INFINITE LOOP (3 messages)
• How do I change this PROC SQL code for SAS 9.3
• How to change FONT in annotatation facility
• How to extract a date variable with where condition (5 messages)
• I need Gradient color shading in red,yellow and green sas annotation facility
• Is there a benchmarking best practices sasCommunity.org article?
• Macro to export to csv (6 messages)
• OT: End of OLEDB on SQL Server
• One Minute intervals (6 messages)
• P. Bourdages est absent
• PROC REPORT: Change Background Color for Cells with Non-Missing Data Without Specifying Variable Names (4 messages)
• Proc SQL efficiency help needed (7 messages)
• Q: need to nest PDF bookmarks (6 messages)
• SAS Bug? Special characters & the end-of-file? (16 messages)
• SAS Stored Processes: 3 Tips to Improve Your Prompts
• SAS as a Windows Service (3 messages)
• SAS random record selection (8 messages)
• SAS to ECL conversion
• SAS/CONNECT piping halts
• Upper and Lower degrees of freedom (6 messages)
• Workshop: R for SAS, SPSS, Stata Users
• burn-in process in simulating time series data (2 messages)
• creating superscript and subscript in SGPLOT (6 messages)
• datastep matching obs problem (5 messages)
• glot - groups on the x axis (4 messages)
• helps for MySQL/ODBC
• how to deal with invalid data when reading large raw data (9 messages)
• how to touch triangle symbol exactly below BAR (2 messages)
• insert blanks (18 messages)
• proc glimmix results output (3 messages)
• proc import causes crash (5 messages)
• proc sql question (2 messages)
• q values in logistic? (5 messages)
• strange behavior of code (14 messages)
• transparency background (5 messages)
• universal viewer 1.2 (9.3) (3 messages)
• using tranwrd to eliminate substrings (10 messages)
• where also statement (5 messages)

1. 2 SAS Professionals Needed Immediately For Contract Work--Rates $100+/Hour
   • 2 SAS Professionals Needed Immediately For Contract Work--Rates $100+/Hour (119 lines)
     From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

2. 90 instances of SAS display manager
   • 90 instances of SAS display manager (13 lines)
     From: Peter Timusk <petertimusk@PROGRAMDOCUMENTATION.COM>
   • Re: 90 instances of SAS display manager (35 lines)
     From: Joe Matise <snoopy369@GMAIL.COM>
   • Re: 90 instances of SAS display manager (46 lines)
     From: Peter Timusk <petertimusk@PROGRAMDOCUMENTATION.COM>
   • Re: 90 instances of SAS display manager (33 lines)
     From: Arthur Tabachneck <art297@ROGERS.COM>

3. Analytic job openings available in exciting new area within healthcare: Payment Innovation
   • Analytic job openings available in exciting new area within healthcare: Payment Innovation (43 lines)
     From: Chaitovsky, Avi-Gil <Avi-Gil.Chaitovsky@ANTHEM.COM>

4. Automatic reply: How to change FONT in annotatation facility
   • Automatic reply: How to change FONT in annotatation facility (14 lines)
     From: Hong Qin <HQin@MERKLEINC.COM>

5. Automatic reply: SAS-L Digest - 14 May 2012 to 15 May 2012 (#2012-354)
   • Automatic reply: SAS-L Digest - 14 May 2012 to 15 May 2012 (#2012-354) (18 lines)
     From: Greg Yamashiro <gryamash@KSBE.EDU>
   • Automatic reply: SAS-L Digest - 14 May 2012 to 15 May 2012 (#2012-354) (28 lines)
     From: Gruver, Deena <dgruver@GERON.COM>

6. Automatic reply: SAS-L Digest - 17 May 2012 to 18 May 2012 (#2012-367)
   • Automatic reply: SAS-L Digest - 17 May 2012 to 18 May 2012 (#2012-367) (18 lines)
     From: Greg Yamashiro <gryamash@KSBE.EDU>

7. Automatic reply: SAS-L Digest - 18 May 2012 - Special issue (#2012-368)
   • Automatic reply: SAS-L Digest - 18 May 2012 - Special issue (#2012-368) (20 lines)
     From: Carol Olson <Carol.Olson@MEREDITH.COM>

8. Automatic reply: insert blanks
   • Automatic reply: insert blanks (22 lines)
     From: Mahometa, Michael J <michael.mahometa@SSC.UTEXAS.EDU>

9. Bricolage Report: SQL Tricks
   • Bricolage Report: SQL Tricks (16 lines)
     From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV>

10. Checking memory use by a SAS process
    • Checking memory use by a SAS process (30 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>

11. DEFINE INFINITE LOOP
    • DEFINE INFINITE LOOP (48 lines)
      From: Bin Zhu <bxz01@HEALTH.STATE.NY.US>
    • Re: DEFINE INFINITE LOOP (75 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: DEFINE INFINITE LOOP (86 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: DEFINE INFINITE LOOP (123 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: DEFINE INFINITE LOOP (156 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: DEFINE INFINITE LOOP (205 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: DEFINE INFINITE LOOP (32 lines)
      From: Bin Zhu <bxz01@HEALTH.STATE.NY.US>
    • Re: DEFINE INFINITE LOOP (253 lines)
      From: Bian, Haikuo <HBian@FLQIO.SDPS.ORG>
    • Re: DEFINE INFINITE LOOP (265 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: DEFINE INFINITE LOOP (100 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>

12. Detecting the Windows date format
    • Detecting the Windows date format (23 lines)
      From: Lorne Klassen <lk1@ROGERS.COM>
    • Re: Detecting the Windows date format (38 lines)
      From: Fehd, Ronald J. (CDC/OCOO/OCIO) <rjf2@CDC.GOV>
    • Re: Detecting the Windows date format (42 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>
    • Re: Detecting the Windows date format (37 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Detecting the Windows date format (77 lines)
      From: Chris Hemedinger <Chris.Hemedinger@SAS.COM>
    • Re: Detecting the Windows date format (90 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: Detecting the Windows date format (122 lines)
      From: Joe DeShon <joedeshon@COMCAST.NET>
    • Re: Detecting the Windows date format (124 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Detecting the Windows date format (140 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: Detecting the Windows date format (130 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>

13. Extract id's with multiple
    • Extract id's with multiple (37 lines)
      From: Asante, Abena <Abena.Asante@CIBC.COM>
    • Re: Extract id's with multiple (74 lines)
      From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US>
    • Re: Extract id's with multiple (22 lines)
      From: Peterson, Stephanie M. [RO HCPR] <Peterson.Stephanie2@MAYO.EDU>
    • Re: Extract id's with multiple (16 lines)
      From: Kim Brown <kibrown@LADHS.ORG>
    • Re: Extract id's with multiple (73 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Extract id's with multiple (81 lines)
      From: Doug Fuller <doug.fuller@ARBORRESEARCH.ORG>
    • Re: Extract id's with multiple (84 lines)
      From: Asante, Abena <Abena.Asante@CIBC.COM>

14. For each obs, find the variable that contains the min value
    • For each obs, find the variable that contains the min value (17 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: For each obs, find the variable that contains the min value (54 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: For each obs, find the variable that contains the min value (37 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: For each obs, find the variable that contains the min value (67 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: For each obs, find the variable that contains the min value (81 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: For each obs, find the variable that contains the min value (73 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: For each obs, find the variable that contains the min value (24 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: For each obs, find the variable that contains the min value (91 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: For each obs, find the variable that contains the min value (100 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: For each obs, find the variable that contains the min value (37 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: For each obs, find the variable that contains the min value (86 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: For each obs, find the variable that contains the min value (95 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

15. Fw: DEFINE INFINITE LOOP
    • Fw: DEFINE INFINITE LOOP (17 lines)
      From: Bin Zhu <bxz01@HEALTH.STATE.NY.US>
    • Re: Fw: DEFINE INFINITE LOOP (129 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: Fw: DEFINE INFINITE LOOP (16 lines)
      From: Bin Zhu <bxz01@HEALTH.STATE.NY.US>

16. How do I change this PROC SQL code for SAS 9.3
    • How do I change this PROC SQL code for SAS 9.3 (30 lines)
      From: Andrea Zimmerman <sassywench74va@GMAIL.COM>

17. How to change FONT in annotatation facility
    • How to change FONT in annotatation facility (124 lines)
      From: SAS Analyst <analystprasad@YAHOO.CO.IN>

18. How to extract a date variable with where condition
    • How to extract a date variable with where condition (56 lines)
      From: Mirisage Fernando <neilfrnnd@GMAIL.COM>
    • Re: How to extract a date variable with where condition (68 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: How to extract a date variable with where condition (89 lines)
      From: MAHESH <peesari.mahesh@GMAIL.COM>
    • Re: How to extract a date variable with where condition (77 lines)
      From: Mirisage Fernando <neilfrnnd@GMAIL.COM>
    • Re: How to extract a date variable with where condition (100 lines)
      From: Mirisage Fernando <neilfrnnd@GMAIL.COM>

19. I need Gradient color shading in red,yellow and green sas annotation facility
    • I need Gradient color shading in red,yellow and green sas annotation facility (34 lines)
      From: SAS Analyst <analystprasad@YAHOO.CO.IN>

20. Is there a benchmarking best practices sasCommunity.org article?
    • Is there a benchmarking best practices sasCommunity.org article? (10 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

21. Macro to export to csv
    • Macro to export to csv (24 lines)
      From: Randy <randistan69@HOTMAIL.COM>
    • Re: Macro to export to csv (64 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Macro to export to csv (15 lines)
      From: Jerome <jerome.masset@CEGEDIM.FR>
    • Re: Macro to export to csv (20 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Macro to export to csv (34 lines)
      From: Burgess, Otto <OBurgess@ATPCO.NET>
    • Re: Macro to export to csv (52 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

22. OT: End of OLEDB on SQL Server
    • OT: End of OLEDB on SQL Server (39 lines)
      From: Alan Churchill <savian.net@GMAIL.COM>

23. One Minute intervals
    • One Minute intervals (19 lines)
      From: Randy <randistan69@HOTMAIL.COM>
    • Re: One Minute intervals (45 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Re: One Minute intervals (50 lines)
      From: Randy <randistan69@HOTMAIL.COM>
    • Re: One Minute intervals (16 lines)
      From: James B <Osprey06@GMAIL.COM>
    • Re: One Minute intervals (76 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Re: One Minute intervals (59 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>

24. P. Bourdages est absent
    • P. Bourdages est absent (9 lines)
      From: Patrice Bourdages <patrice.bourdages@DGAG.CA>

25. PROC REPORT: Change Background Color for Cells with Non-Missing Data Without Specifying Variable Names
    • PROC REPORT: Change Background Color for Cells with Non-Missing Data Without Specifying Variable Names (84 lines)
      From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>
    • Re: PROC REPORT: Change Background Color for Cells with Non-Missing Data Without Specifying Variable Names (105 lines)
      From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>
    • Re: PROC REPORT: Change Background Color for Cells with Non-Missing Data Without Specifying Variable Names (143 lines)
      From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>
    • Re: PROC REPORT: Change Background Color for Cells with Non-Missing Data Without Specifying Variable Names (93 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>

26. Proc SQL efficiency help needed
    • Proc SQL efficiency help needed (35 lines)
      From: Dave <david.brewer@UC.EDU>
    • Re: Proc SQL efficiency help needed (69 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Proc SQL efficiency help needed (75 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: Proc SQL efficiency help needed (52 lines)
      From: Sigurd W. Hermansen <hermans1@WESTAT.COM>
    • Re: Proc SQL efficiency help needed (121 lines)
      From: Tolbert, William <tolbert.w@GHC.ORG>
    • Re: Proc SQL efficiency help needed (83 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: Proc SQL efficiency help needed (13 lines)
      From: Sigurd W. Hermansen <hermans1@WESTAT.COM>

27. Q: need to nest PDF bookmarks
    • Re: Q: need to nest PDF bookmarks (59 lines)
      From: Roland Berry <rolandberry@HOTMAIL.COM>
    • Re: Q: need to nest PDF bookmarks (9 lines)
      From: Roland Berry <rolandberry@HOTMAIL.COM>
    • Re: Q: need to nest PDF bookmarks (24 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: Q: need to nest PDF bookmarks (41 lines)
      From: Roland Berry <rolandberry@HOTMAIL.COM>
    • Re: Q: need to nest PDF bookmarks (99 lines)
      From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
    • Re: Q: need to nest PDF bookmarks (7 lines)
      From: Roland Berry <rolandberry@HOTMAIL.COM>

28. SAS Bug? Special characters & the end-of-file?
    • SAS Bug? Special characters & the end-of-file? (63 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: SAS Bug? Special characters & the end-of-file? (79 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: SAS Bug? Special characters & the end-of-file? (81 lines)
      From: Paul Hamilton <pdhamilton1@COMCAST.NET>
    • Re: SAS Bug? Special characters & the end-of-file? (86 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: SAS Bug? Special characters & the end-of-file? (94 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: SAS Bug? Special characters & the end-of-file? (104 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: SAS Bug? Special characters & the end-of-file? (104 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: SAS Bug? Special characters & the end-of-file? (116 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • SAS Bug? Special characters & the end-of-file? (58 lines)
      From: Paul Hamilton <pdhamilton1@COMCAST.NET>
    • Re: SAS Bug? Special characters & the end-of-file? (73 lines)
      From: Choate, Paul@DDS <Paul.Choate@DDS.CA.GOV>
    • Re: SAS Bug? Special characters & the end-of-file? (93 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: SAS Bug? Special characters & the end-of-file? (117 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: SAS Bug? Special characters & the end-of-file? (95 lines)
      From: William W. Viergever <william@VIERGEVER.NET>
    • Re: SAS Bug? Special characters & the end-of-file? (130 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: SAS Bug? Special characters & the end-of-file? (161 lines)
      From: William W. Viergever <william@VIERGEVER.NET>
    • Re: SAS Bug? Special characters & the end-of-file? (171 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

29. SAS Stored Processes: 3 Tips to Improve Your Prompts
    • SAS Stored Processes: 3 Tips to Improve Your Prompts (13 lines)
      From: Vincent Granville <vincentg@DATASHAPING.COM>

30. SAS as a Windows Service
    • SAS as a Windows Service (15 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: SAS as a Windows Service (64 lines)
      From: Michael Davis <michael@BASSETTCONSULTING.COM>
    • Re: SAS as a Windows Service (44 lines)
      From: Alan Churchill <savian.net@GMAIL.COM>

31. SAS random record selection
    • SAS random record selection (13 lines)
      From: Kathleen Askland <k.askland@GMAIL.COM>
    • Re: SAS random record selection (57 lines)
      From: Mary <mlhoward@AVALON.NET>
    • SAS random record selection (15 lines)
      From: Kathleen Askland <k.askland@GMAIL.COM>
    • Re: SAS random record selection (29 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: SAS random record selection (46 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: SAS random record selection (75 lines)
      From: Mary <mlhoward@AVALON.NET>
    • Re: SAS random record selection (28 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>
    • Re: SAS random record selection (20 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>

32. SAS to ECL conversion
    • SAS to ECL conversion (15 lines)
      From: polyphonic48@gmail.com <polyphonic48@GMAIL.COM>

33. SAS/CONNECT piping halts
    • SAS/CONNECT piping halts (466 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>

34. Upper and Lower degrees of freedom
    • Upper and Lower degrees of freedom (53 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: Upper and Lower degrees of freedom (70 lines)
      From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>
    • Re: Upper and Lower degrees of freedom (76 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: Upper and Lower degrees of freedom (93 lines)
      From: Bhupinder Singh Farmaha <bhupi80singh@YAHOO.CO.IN>
    • Re: Upper and Lower degrees of freedom (142 lines)
      From: SAS_learner <proccontents@GMAIL.COM>
    • Re: Upper and Lower degrees of freedom (189 lines)
      From: SAS_learner <proccontents@GMAIL.COM>

35. Workshop: R for SAS, SPSS, Stata Users
    • Workshop: R for SAS, SPSS, Stata Users (29 lines)
      From: Muenchen, Robert A (Bob) <muenchen@UTK.EDU>

36. burn-in process in simulating time series data
    • burn-in process in simulating time series data (20 lines)
      From: =?UTF-8?B?6aG+6aOe?= <gufei1984@GMAIL.COM>
    • Re: burn-in process in simulating time series data (30 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>

37. creating superscript and subscript in SGPLOT
    • creating superscript and subscript in SGPLOT (24 lines)
      From: Farmaha Bhupinder <bhupi80singh@YAHOO.CO.IN>
    • Re: creating superscript and subscript in SGPLOT (53 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: creating superscript and subscript in SGPLOT (131 lines)
      From: Farmaha Bhupinder <bhupi80singh@YAHOO.CO.IN>
    • Re: creating superscript and subscript in SGPLOT (176 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: creating superscript and subscript in SGPLOT (144 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>
    • Re: creating superscript and subscript in SGPLOT (185 lines)
      From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>

38. datastep matching obs problem
    • datastep matching obs problem (35 lines)
      From: JD <jdiebal@GMAIL.COM>
    • Re: datastep matching obs problem (73 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: datastep matching obs problem (121 lines)
      From: JD <jdiebal@GMAIL.COM>
    • Re: datastep matching obs problem (122 lines)
      From: J <jdiebal@GMAIL.COM>
    • Re: datastep matching obs problem (174 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

39. glot - groups on the x axis
    • glot - groups on the x axis (17 lines)
      From: Treder, David <dtreder@GENESEEISD.ORG>
    • Re: glot - groups on the x axis (36 lines)
      From: High, Robin R <rhigh@UNMC.EDU>
    • Re: glot - groups on the x axis (88 lines)
      From: Treder, David <dtreder@GENESEEISD.ORG>
    • Re: glot - groups on the x axis (167 lines)
      From: Treder, David <dtreder@GENESEEISD.ORG>

40. helps for MySQL/ODBC
    • helps for MySQL/ODBC (38 lines)
      From: Hong Yang <hong.yang550@GMAIL.COM>

41. how to deal with invalid data when reading large raw data
    • Re: how to deal with invalid data when reading large raw data (66 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: how to deal with invalid data when reading large raw data (118 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: how to deal with invalid data when reading large raw data (193 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: how to deal with invalid data when reading large raw data (234 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: how to deal with invalid data when reading large raw data (265 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: how to deal with invalid data when reading large raw data (287 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: how to deal with invalid data when reading large raw data (308 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: how to deal with invalid data when reading large raw data (112 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: how to deal with invalid data when reading large raw data (327 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

42. how to touch triangle symbol exactly below BAR
    • how to touch triangle symbol exactly below BAR (52 lines)
      From: SAS Analyst <analystprasad@YAHOO.CO.IN>
    • Re: how to touch triangle symbol exactly below BAR (69 lines)
      From: Nat Wooding <nathani@VERIZON.NET>

43. insert blanks
    • insert blanks (29 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: insert blanks (37 lines)
      From: Fareeza Khurshed <fkhurshed@GMAIL.COM>
    • Re: insert blanks (44 lines)
      From: Yuewei Liu <contact@YUEWEILIU.COM>
    • Re: insert blanks (75 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: insert blanks (82 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: insert blanks (96 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: insert blanks (72 lines)
      From: Ken Borowiak <evilpettingzoo97@AOL.COM>
    • Re: insert blanks (85 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: insert blanks (101 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Re: insert blanks (113 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: insert blanks (56 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: insert blanks (68 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: insert blanks (97 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: insert blanks (90 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: insert blanks (107 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: insert blanks (73 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: insert blanks (52 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>
    • Re: insert blanks (71 lines)
      From: Daniel Nordlund <djnordlund@FRONTIER.COM>

44. proc glimmix results output
    • proc glimmix results output (49 lines)
      From: Soumi <soumiray74@GMAIL.COM>
    • Re: proc glimmix results output (43 lines)
      From: Steve Denham <stevedrd@YAHOO.COM>
    • Re: proc glimmix results output (77 lines)
      From: Peter Flom <peterflomconsulting@MINDSPRING.COM>

45. proc import causes crash
    • proc import causes crash (32 lines)
      From: Pirritano, Matthew J <PirritanoM@AETNA.COM>
    • Re: proc import causes crash (66 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: proc import causes crash (67 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: proc import causes crash (86 lines)
      From: Pirritano, Matthew J <PirritanoM@AETNA.COM>
    • Re: proc import causes crash (84 lines)
      From: Pirritano, Matthew J <PirritanoM@AETNA.COM>

46. proc sql question
    • proc sql question (35 lines)
      From: Masoud Pajoh <mpajoh@ODOT.ORG>
    • Re: proc sql question (52 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>

47. q values in logistic?
    • q values in logistic? (21 lines)
      From: Dennis Fisher <Dennis.Fisher@CSULB.EDU>
    • Re: q values in logistic? (23 lines)
      From: Steve Denham <stevedrd@YAHOO.COM>
    • Re: q values in logistic? (59 lines)
      From: Dennis Fisher <Dennis.Fisher@CSULB.EDU>
    • Re: q values in logistic? (87 lines)
      From: Bhupinder Farmaha <bhupi80singh@YAHOO.CO.IN>
    • Re: q values in logistic? (109 lines)
      From: Dennis Fisher <Dennis.Fisher@CSULB.EDU>

48. strange behavior of code
    • strange behavior of code (114 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: strange behavior of code (116 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: strange behavior of code (8 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: strange behavior of code (142 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: strange behavior of code (140 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: strange behavior of code (158 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: strange behavior of code (163 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: strange behavior of code (174 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: strange behavior of code (176 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: strange behavior of code (185 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: strange behavior of code (255 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: strange behavior of code (271 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: strange behavior of code (290 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: strange behavior of code (293 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>

49. transparency background
    • transparency background (14 lines)
      From: Ben <benpub7@YAHOO.COM>
    • Re: transparency background (7 lines)
      From: Ben <benpub7@YAHOO.COM>
    • Re: transparency background (21 lines)
      From: Ben <benpub7@YAHOO.COM>
    • Re: transparency background (43 lines)
      From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>
    • Re: transparency background (37 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>

50. universal viewer 1.2 (9.3)
    • universal viewer 1.2 (9.3) (53 lines)
      From: Andre Wielki <wielki@INED.FR>
    • Re: universal viewer 1.2 (9.3) (69 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: universal viewer 1.2 (9.3) (51 lines)
      From: Andre Wielki <wielki@INED.FR>

51. using tranwrd to eliminate substrings
    • using tranwrd to eliminate substrings (56 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: using tranwrd to eliminate substrings (65 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: using tranwrd to eliminate substrings (81 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: using tranwrd to eliminate substrings (89 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: using tranwrd to eliminate substrings (65 lines)
      From: bbser 2009 <bbser2009@GMAIL.COM>
    • Re: using tranwrd to eliminate substrings (70 lines)
      From: Ya Huang <ya.huang@AMYLIN.COM>
    • Re: using tranwrd to eliminate substrings (96 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: using tranwrd to eliminate substrings (113 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: using tranwrd to eliminate substrings (136 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: using tranwrd to eliminate substrings (144 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

52. where also statement
    • Re: where also statement (58 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: where also statement (67 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: where also statement (167 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: where also statement (76 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: where also statement (96 lines)
      From: Mary Rosenbloom <mary.rosenbloom.sas@GMAIL.COM>