Table of contents:

• "freqsept" parameters in %unistats
• <No subject>
• AF clear fields (2 messages)
• ANCOVA vs. longitudinal (2 messages)
• Automatic reply: Bitwise function in SAS
• Automatic reply: Determining which element of an array has the desired value
• Automatic reply: SAS-L Digest - 31 Mar 2012 to 1 Apr 2012 (#2012-230)
• Automatic reply: SAS-L Digest - 4 Apr 2012 - Special issue (#2012-239)
• Automatic reply: SAS-L Digest - 4 Apr 2012 to 5 Apr 2012 (#2012-240)
• Automatic reply: SAS-L Digest - 5 Apr 2012 - Special issue (#2012-241)
• Automatic reply: SAS-L Digest - 6 Apr 2012 - Special issue (#2012-243)
• Bitwise function in SAS
• Blazing WORK library performance with an accelerator card
• Burger King & SAS
• Comparing Across Rows: PROC SQL
• Compressing Pooled Datasets
• Conversion to SPSS in 9.3 (3 messages)
• DS2 comments? (2 messages)
• Data Programmer position
• Determining which element of an array has the desired value (17 messages)
• Does PROC DATASETS rebuild indexes? (6 messages)
• Dynamically Flagging time-ordered turning points based on Standard deviation!
• Effort Estimation (2 messages)
• FW: PharmaSUG 2012 Early Registration discount ends TODAY!!!
• Grouping (3 messages)
• How can I tell were our Work library is? (7 messages)
• ICD-9/10 codes on Death Certificate (6 messages)
• Import and Export bug fixed in SAS 9.3
• Improving bootstrap performance of sas code
• Inserting blank rows (7 messages)
• LIST statement, was: RE: (2 messages)
• LIST statement, was: RE: Ruler
• Macro Evaulation problem (4 messages)
• Matched case-contol: m to 1 cases/controls:proc phreg
• Modelling proportions in SAS (2 messages)
• ODBC to Excel From SAS
• OT: Friday Humor (2 messages)
• Omitting rows in PROC REPORT without affecting sums? (3 messages)
• POWER: TwoSampleFreq Ho: p1 <= p2 (2 messages)
• SAS : Help in 'dating' (10 messages)
• SAS MARKETING CAMPAIGN cslt role in St. Louis, MO
• SAS MIGRATION ADMINISTRATOR - Richmond, VA
• SAS macro design and the "Separation of Concerns" (7 messages)
• SAS-L Meetup (formerly BOF)
• SGF 2012 Proceedings ALREADY Available (6 messages)
• Summer Online: Learn to Program in R Language
• Unit-Weighted Regression
• Using replace option with Excel and proc export (3 messages)
• Variable Transformations (2 messages)
• converting the results of a SAS function to a macrovariable (3 messages)
• group by in SQL (4 messages)
• grouse about 64 bit machine (19 messages)
• help on macro (6 messages)
• include with large text field (7 messages)
• macro evalation problem: A character operand was found in the %EVAL function or %IF condition where a numeric (2 messages)
• ruler
• storing SQL results in multiple macro variables at once (2 messages)
• storing SQL results in multiple macro variables at once - solved
• using a 1x1 vector in PROC IML as an index in a do loop (3 messages)

1. "freqsept" parameters in %unistats
   • "freqsept" parameters in %unistats (26 lines)
     From: Roland Berry <rolandberry@HOTMAIL.COM>

2. <No subject>
   • <No subject> (21 lines)
     From: Arthur Pashi <artpshhealth@HOTMAIL.COM>

3. AF clear fields
   • AF clear fields (39 lines)
     From: Quentin McMullen <qmcmullen.sas@GMAIL.COM>
   • Re: AF clear fields (54 lines)
     From: DUELL, BOB <bd9439@ATT.COM>

4. ANCOVA vs. longitudinal
   • Re: ANCOVA vs. longitudinal (62 lines)
     From: William Shakespeare <shakespeare_1040@HOTMAIL.COM>
   • Re: ANCOVA vs. longitudinal (79 lines)
     From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>

5. Automatic reply: Bitwise function in SAS
   • Automatic reply: Bitwise function in SAS (13 lines)
     From: Harder, Jeff <Jeff.Harder@INFARMBUREAU.COM>

6. Automatic reply: Determining which element of an array has the desired value
   • Automatic reply: Determining which element of an array has the desired value (15 lines)
     From: Joe Morrissey <Joe.Morrissey@SAS.COM>

7. Automatic reply: SAS-L Digest - 31 Mar 2012 to 1 Apr 2012 (#2012-230)
   • Automatic reply: SAS-L Digest - 31 Mar 2012 to 1 Apr 2012 (#2012-230) (16 lines)
     From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU>

8. Automatic reply: SAS-L Digest - 4 Apr 2012 - Special issue (#2012-239)
   • Automatic reply: SAS-L Digest - 4 Apr 2012 - Special issue (#2012-239) (17 lines)
     From: Bryson, Jennifer <Jennifer.Bryson@COVIDIEN.COM>

9. Automatic reply: SAS-L Digest - 4 Apr 2012 to 5 Apr 2012 (#2012-240)
   • Automatic reply: SAS-L Digest - 4 Apr 2012 to 5 Apr 2012 (#2012-240) (14 lines)
     From: Erika Steinmetz <esteinmetz@AAMC.ORG>

10. Automatic reply: SAS-L Digest - 5 Apr 2012 - Special issue (#2012-241)
    • Automatic reply: SAS-L Digest - 5 Apr 2012 - Special issue (#2012-241) (16 lines)
      From: Alan Elliott <Alan.Elliott@UTSOUTHWESTERN.EDU>

11. Automatic reply: SAS-L Digest - 6 Apr 2012 - Special issue (#2012-243)
    • Automatic reply: SAS-L Digest - 6 Apr 2012 - Special issue (#2012-243) (22 lines)
      From: Carol Olson <Carol.Olson@MEREDITH.COM>

12. Bitwise function in SAS
    • Re: Bitwise function in SAS (215 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>

13. Blazing WORK library performance with an accelerator card
    • Blazing WORK library performance with an accelerator card (24 lines)
      From: Roland Berry <rolandberry@HOTMAIL.COM>

14. Burger King & SAS
    • Burger King & SAS (15 lines)
      From: Joe Whitehurst <joewhitehurst@GMAIL.COM>

15. Comparing Across Rows: PROC SQL
    • Re: Comparing Across Rows: PROC SQL (9 lines)
      From: Ross Clark <rosscharlesclark@GMAIL.COM>

16. Compressing Pooled Datasets
    • Compressing Pooled Datasets (16 lines)
      From: Roland Berry <rolandberry@HOTMAIL.COM>

17. Conversion to SPSS in 9.3
    • Conversion to SPSS in 9.3 (22 lines)
      From: Dennis Fisher <Dennis.Fisher@CSULB.EDU>
    • Re: Conversion to SPSS in 9.3 (29 lines)
      From: F J Kelley <jkelley@UGA.EDU>
    • Re: Conversion to SPSS in 9.3 (41 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

18. DS2 comments?
    • DS2 comments? (22 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: DS2 comments? (65 lines)
      From: Alan Churchill <savian.net@GMAIL.COM>

19. Data Programmer position
    • Data Programmer position (41 lines)
      From: Susanne M. Sardella <susanne.sardella@COGNIGENCORP.COM>

20. Determining which element of an array has the desired value
    • Determining which element of an array has the desired value (47 lines)
      From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM>
    • Re: Determining which element of an array has the desired value (102 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Determining which element of an array has the desired value (129 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Determining which element of an array has the desired value (59 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Determining which element of an array has the desired value (121 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: Determining which element of an array has the desired value (28 lines)
      From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM>
    • Re: Determining which element of an array has the desired value (68 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: Determining which element of an array has the desired value (52 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: Determining which element of an array has the desired value (69 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Determining which element of an array has the desired value (85 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: Determining which element of an array has the desired value (50 lines)
      From: Nat Wooding <nathani@VERIZON.NET>
    • Re: Determining which element of an array has the desired value (105 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: Determining which element of an array has the desired value (87 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Determining which element of an array has the desired value (108 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: Determining which element of an array has the desired value (163 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Determining which element of an array has the desired value (115 lines)
      From: Chang Chung <chang_y_chung@HOTMAIL.COM>
    • Re: Determining which element of an array has the desired value (23 lines)
      From: Andrew Karp/Sierra Information Services <sierrainfo@AOL.COM>

21. Does PROC DATASETS rebuild indexes?
    • Does PROC DATASETS rebuild indexes? (48 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Does PROC DATASETS rebuild indexes? (82 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Does PROC DATASETS rebuild indexes? (103 lines)
      From: DUELL, BOB <bd9439@ATT.COM>
    • Re: Does PROC DATASETS rebuild indexes? (119 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Does PROC DATASETS rebuild indexes? (124 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: Does PROC DATASETS rebuild indexes? (133 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>

22. Dynamically Flagging time-ordered turning points based on Standard deviation!
    • Re: Dynamically Flagging time-ordered turning points based on Standard deviation! (44 lines)
      From: Shyamprasad Samisetti <shyam.cbz@GMAIL.COM>

23. Effort Estimation
    • Effort Estimation (34 lines)
      From: Sridhar, Nagakumar <Nagakumar.Sridhar@RBSCITIZENS.COM>
    • Re: Effort Estimation (16 lines)
      From: Rick Wicklin <Rick.Wicklin@SAS.COM>

24. FW: PharmaSUG 2012 Early Registration discount ends TODAY!!!
    • FW: PharmaSUG 2012 Early Registration discount ends TODAY!!! (59 lines)
      From: Richard Read Allen <peakstat@WISPERTEL.NET>

25. Grouping
    • Grouping (36 lines)
      From: Val Krem <valkrem@YAHOO.COM>
    • Re: Grouping (50 lines)
      From: Fareeza Khurshed <fkhurshed@GMAIL.COM>
    • Re: Grouping (62 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>

26. How can I tell were our Work library is?
    • How can I tell were our Work library is? (21 lines)
      From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US>
    • Re: How can I tell were our Work library is? (26 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: How can I tell were our Work library is? (24 lines)
      From: Sterling Paramore <gnilrets@GMAIL.COM>
    • Re: How can I tell were our Work library is? (39 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
    • Re: How can I tell were our Work library is? (42 lines)
      From: Gerstle, John (CDC/OID/NCHHSTP) <yzg9@CDC.GOV>
    • Re: How can I tell were our Work library is? (48 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: How can I tell were our Work library is? (13 lines)
      From: Durrett, Cindy <CindyDurrett@FDLE.STATE.FL.US>

27. ICD-9/10 codes on Death Certificate
    • ICD-9/10 codes on Death Certificate (69 lines)
      From: John Parker <John.V.Parker@KP.ORG>
    • Re: ICD-9/10 codes on Death Certificate (79 lines)
      From: Data _null_; <iebupdte@GMAIL.COM>
    • Re: ICD-9/10 codes on Death Certificate (129 lines)
      From: John Parker <John.V.Parker@KP.ORG>
    • Re: ICD-9/10 codes on Death Certificate (97 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
    • Re: ICD-9/10 codes on Death Certificate (31 lines)
      From: James, Steve (CDC/OID/OD) <spj1@CDC.GOV>
    • Re: ICD-9/10 codes on Death Certificate (131 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>

28. Import and Export bug fixed in SAS 9.3
    • Import and Export bug fixed in SAS 9.3 (29 lines)
      From: DUELL, BOB <bd9439@ATT.COM>

29. Improving bootstrap performance of sas code
    • Re: Improving bootstrap performance of sas code (66 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

30. Inserting blank rows
    • Inserting blank rows (55 lines)
      From: Randy <randistan69@HOTMAIL.COM>
    • Re: Inserting blank rows (111 lines)
      From: Vasanth S <vasanthz@GMAIL.COM>
    • Re: Inserting blank rows (84 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
    • Re: Inserting blank rows (93 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Inserting blank rows (103 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: Inserting blank rows (24 lines)
      From: Pradeep <chittiprolupradeep@GMAIL.COM>
    • Re: Inserting blank rows (14 lines)
      From: Randy <randistan69@HOTMAIL.COM>

31. LIST statement, was: RE:
    • LIST statement, was: RE: (38 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: LIST statement, was: RE: (47 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>

32. LIST statement, was: RE: Ruler
    • Re: LIST statement, was: RE: Ruler (101 lines)
      From: Arthur Pashi <artpshhealth@HOTMAIL.COM>

33. Macro Evaulation problem
    • Macro Evaulation problem (50 lines)
      From: Randall Powers <powers_r@BLS.GOV>
    • Re: Macro Evaulation problem (81 lines)
      From: Randall Powers <powers_r@BLS.GOV>
    • Re: Macro Evaulation problem (108 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Macro Evaulation problem (90 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>

34. Matched case-contol: m to 1 cases/controls:proc phreg
    • Matched case-contol: m to 1 cases/controls:proc phreg (33 lines)
      From: Abdelouahid Tajar <a_tajar@HOTMAIL.CO.UK>

35. Modelling proportions in SAS
    • Modelling proportions in SAS (28 lines)
      From: Ronald McDowell <McDowell-R3@EMAIL.ULSTER.AC.UK>
    • Re: Modelling proportions in SAS (35 lines)
      From: oloolo <dynamicpanel@YAHOO.COM>

36. ODBC to Excel From SAS
    • ODBC to Excel From SAS (8 lines)
      From: Doug <doug.leonard@WYO.GOV>

37. OT: Friday Humor
    • OT: Friday Humor (34 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • OT: Friday Humor (38 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>

38. Omitting rows in PROC REPORT without affecting sums?
    • Omitting rows in PROC REPORT without affecting sums? (70 lines)
      From: Jerome Solanum <Jerome.Solanum@GMAIL.COM>
    • Re: Omitting rows in PROC REPORT without affecting sums? (93 lines)
      From: Yu Zhang <zhangyu05@GMAIL.COM>
    • Re: Omitting rows in PROC REPORT without affecting sums? (96 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

39. POWER: TwoSampleFreq Ho: p1 <= p2
    • POWER: TwoSampleFreq Ho: p1 <= p2 (34 lines)
      From: Citam <citam.sasl@GMAIL.COM>
    • Re: POWER: TwoSampleFreq Ho: p1 <= p2 (53 lines)
      From: Citam <citam.sasl@GMAIL.COM>

40. SAS : Help in 'dating'
    • SAS : Help in 'dating' (57 lines)
      From: Vasanth S <vasanthz@GMAIL.COM>
    • Re: SAS : Help in 'dating' (125 lines)
      From: Vasanth S <vasanthz@GMAIL.COM>
    • Re: SAS : Help in 'dating' (95 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
    • Re: SAS : Help in 'dating' (73 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: SAS : Help in 'dating' (97 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
    • Re: SAS : Help in 'dating' (53 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: SAS : Help in 'dating' (168 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
    • Re: SAS : Help in 'dating' (132 lines)
      From: Fried Egg <friedegg2012@GMAIL.COM>
    • Re: SAS : Help in 'dating' (94 lines)
      From: Vasanth S <vasanthz@GMAIL.COM>
    • Re: SAS : Help in 'dating' (96 lines)
      From: Vasanth S <vasanthz@GMAIL.COM>

41. SAS MARKETING CAMPAIGN cslt role in St. Louis, MO
    • SAS MARKETING CAMPAIGN cslt role in St. Louis, MO (90 lines)
      From: Lianne Best <lbest@EEIHR.COM>

42. SAS MIGRATION ADMINISTRATOR - Richmond, VA
    • SAS MIGRATION ADMINISTRATOR - Richmond, VA (43 lines)
      From: Lianne Best <lbest@EEIHR.COM>

43. SAS macro design and the "Separation of Concerns"
    • SAS macro design and the "Separation of Concerns" (14 lines)
      From: Roland Berry <rolandberry@HOTMAIL.COM>
    • Re: SAS macro design and the "Separation of Concerns" (43 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: SAS macro design and the "Separation of Concerns" (8 lines)
      From: Roland Berry <rolandberry@HOTMAIL.COM>
    • Re: SAS macro design and the "Separation of Concerns" (57 lines)
      From: Roland Berry <rolandberry@HOTMAIL.COM>
    • Re: SAS macro design and the "Separation of Concerns" (80 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>
    • Re: SAS macro design and the "Separation of Concerns" (103 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: SAS macro design and the "Separation of Concerns" (38 lines)
      From: Roland Berry <rolandberry@HOTMAIL.COM>

44. SAS-L Meetup (formerly BOF)
    • SAS-L Meetup (formerly BOF) (27 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

45. SGF 2012 Proceedings ALREADY Available
    • SGF 2012 Proceedings ALREADY Available (16 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: SGF 2012 Proceedings ALREADY Available (27 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: SGF 2012 Proceedings ALREADY Available (50 lines)
      From: Kirby, Ted <ted.kirby@LEWIN.COM>
    • Re: SGF 2012 Proceedings ALREADY Available (37 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: SGF 2012 Proceedings ALREADY Available (51 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>
    • Re: SGF 2012 Proceedings ALREADY Available (60 lines)
      From: Arthur Tabachneck <art297@ROGERS.COM>

46. Summer Online: Learn to Program in R Language
    • Summer Online: Learn to Program in R Language (34 lines)
      From: Geoffrey Hubona <ghubona@GMAIL.COM>

47. Unit-Weighted Regression
    • Unit-Weighted Regression (21 lines)
      From: Ross Clark <rosscharlesclark@GMAIL.COM>

48. Using replace option with Excel and proc export
    • Using replace option with Excel and proc export (126 lines)
      From: Joe DeShon <joedeshon@COMCAST.NET>
    • Re: Using replace option with Excel and proc export (141 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: Using replace option with Excel and proc export (169 lines)
      From: Joe DeShon <joedeshon@COMCAST.NET>

49. Variable Transformations
    • Variable Transformations (17 lines)
      From: Reed, Derek <derek.reed@SINCLAIR.EDU>
    • Re: Variable Transformations (24 lines)
      From: Steve Denham <stevedrd@YAHOO.COM>

50. converting the results of a SAS function to a macrovariable
    • converting the results of a SAS function to a macrovariable (45 lines)
      From: Randall Powers <powers_r@BLS.GOV>
    • Re: converting the results of a SAS function to a macrovariable (66 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: converting the results of a SAS function to a macrovariable (84 lines)
      From: SAS LIST <listsas7@GMAIL.COM>

51. group by in SQL
    • group by in SQL (68 lines)
      From: Mirisage Fernando <neilfrnnd@GMAIL.COM>
    • Re: group by in SQL (94 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: group by in SQL (151 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>
    • Re: group by in SQL (165 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>

52. grouse about 64 bit machine
    • grouse about 64 bit machine (18 lines)
      From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>
    • Re: grouse about 64 bit machine (42 lines)
      From: William W. Viergever <william@VIERGEVER.NET>
    • Re: grouse about 64 bit machine (38 lines)
      From: Dennis Fisher <Dennis.Fisher@CSULB.EDU>
    • Re: grouse about 64 bit machine (43 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: grouse about 64 bit machine (62 lines)
      From: Dennis Fisher <Dennis.Fisher@CSULB.EDU>
    • Re: grouse about 64 bit machine (79 lines)
      From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>
    • Re: grouse about 64 bit machine (96 lines)
      From: Dennis Fisher <Dennis.Fisher@CSULB.EDU>
    • Re: grouse about 64 bit machine (47 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: grouse about 64 bit machine (100 lines)
      From: Alan Churchill <savian.net@GMAIL.COM>
    • Re: grouse about 64 bit machine (101 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: grouse about 64 bit machine (119 lines)
      From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV>
    • Re: grouse about 64 bit machine (113 lines)
      From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>
    • Re: grouse about 64 bit machine (119 lines)
      From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>
    • Re: grouse about 64 bit machine (139 lines)
      From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>
    • Re: grouse about 64 bit machine (151 lines)
      From: William W. Viergever <william@VIERGEVER.NET>
    • Re: grouse about 64 bit machine (63 lines)
      From: Alan Churchill <savian.net@GMAIL.COM>
    • Re: grouse about 64 bit machine (170 lines)
      From: Alan Churchill <savian.net@GMAIL.COM>
    • Re: grouse about 64 bit machine (94 lines)
      From: Fehd, Ronald J. (CDC/OCOO/ITSO) <rjf2@CDC.GOV>
    • Re: grouse about 64 bit machine (112 lines)
      From: Swank, Paul R <Paul.R.Swank@UTH.TMC.EDU>

53. help on macro
    • help on macro (44 lines)
      From: J Lee <lrx0208@YAHOO.COM>
    • Re: help on macro (71 lines)
      From: Joe Matise <snoopy369@GMAIL.COM>
    • Re: help on macro (113 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: help on macro (89 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>
    • Re: help on macro (32 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: help on macro (7 lines)
      From: Jason Lee <lrx0208@YAHOO.COM>

54. include with large text field
    • include with large text field (67 lines)
      From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>
    • Re: include with large text field (76 lines)
      From: Keintz, H. Mark <mkeintz@WHARTON.UPENN.EDU>
    • Re: include with large text field (106 lines)
      From: Jason Schoeneberger <jschoeneberger@CAROLINA.RR.COM>
    • Re: include with large text field (127 lines)
      From: Zdeb, Michael S <mzdeb@ALBANY.EDU>
    • Re: include with large text field (118 lines)
      From: Ray Griner <rgriner@SDAC.HARVARD.EDU>
    • Re: include with large text field (87 lines)
      From: Tom Abernathy <tom.abernathy@GMAIL.COM>
    • Re: include with large text field (132 lines)
      From: DUELL, BOB <bd9439@ATT.COM>

55. macro evalation problem: A character operand was found in the %EVAL function or %IF condition where a numeric
    • macro evalation problem: A character operand was found in the %EVAL function or %IF condition where a numeric (55 lines)
      From: Randall Powers <powers_r@BLS.GOV>
    • Re: macro evalation problem: A character operand was found in the %EVAL function or %IF condition where a numeric (91 lines)
      From: toby dunn <tobydunn@HOTMAIL.COM>

56. ruler
    • Re: ruler (52 lines)
      From: Terjeson, Mark <Mterjeson@RUSSELL.COM>

57. storing SQL results in multiple macro variables at once
    • storing SQL results in multiple macro variables at once (105 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>
    • Re: storing SQL results in multiple macro variables at once (116 lines)
      From: Søren Lassen <s.lassen@POST.TELE.DK>

58. storing SQL results in multiple macro variables at once - solved
    • Re: storing SQL results in multiple macro variables at once - solved (130 lines)
      From: Bolotin Yevgeniy <YBolotin@SCHOOLS.NYC.GOV>

59. using a 1x1 vector in PROC IML as an index in a do loop
    • using a 1x1 vector in PROC IML as an index in a do loop (20 lines)
      From: Randall Powers <powers_r@BLS.GOV>
    • Re: using a 1x1 vector in PROC IML as an index in a do loop (39 lines)
      From: Mark Miller <mdhmiller@GMAIL.COM>
    • Re: using a 1x1 vector in PROC IML as an index in a do loop (25 lines)
      From: Rick Wicklin <rick.wicklin@SAS.COM>