5 Air Jordans 4 Air Jordans 4.5 Air Jordans 5 Air Jordans 6 ( paypal payment )( www.315store.com )Air Jordans 7 Air Jordans 8 Air Jordans 9 Air Jordans 10 Air Jordans 11 Air Jordans 12 Air Jordans 13 Air Jordans 14 Air Jordans 16 ( paypal payment5 Air Jordans 4 Air Jordans 4.5 Air Jordans 5 Air Jordans 6 ( paypal payment )( www.315store.com )Air Jordans 7 Air Jordans 8 Air Jordans 9 Air Jordans 10 Air Jordans 11 Air Jordans 12 Air Jordans 13 Air Jordans 14 Air Jordans 16 ( paypal payment (98 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> 64-bit SAS with 32-bit catalogs64-bit SAS with 32-bit catalogs (16 lines) From: Wanda Upole <Wanda_Upole@HGSI.COM> Re: 64-bit SAS with 32-bit catalogs (38 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Acronym convergenceAcronym convergence (22 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Acronym convergence (36 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Acronym convergence (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Acronym convergence (43 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Acronym convergence (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Acronym convergence (91 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Acronym convergence (94 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Add user and password details to autoexec file?Re: Add user and password details to autoexec file? (21 lines) From: Shankar <shankar.stat@GMAIL.COM> Aggregating health care claims dataAggregating health care claims data (33 lines) From: Tom Bohman <tmbohman@GMAIL.COM> Re: Aggregating health care claims data (50 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Bad joke Tuesday...Bad joke Tuesday... (23 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Bad joke Tuesday... (44 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Re: Bad joke Tuesday... (33 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Best Practices in changing Char to SAS DATE TIMEBest Practices in changing Char to SAS DATE TIME (31 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Best Practices in changing Char to SAS DATE TIME (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Best Practices in changing Char to SAS DATE TIME (56 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Better integration solution of Web reportBetter integration solution of Web report (52 lines) From: akar <aakarshanabelard@YAHOO.COM> Bivariate Cumulative DistributionBivariate Cumulative Distribution (34 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (39 lines) From: oloolo <dynamicpanel@YAHOO.COM> Bivariate Cumulative Distribution (178 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (186 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (99 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (197 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (218 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (267 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (13 lines) From: Andrew Kramer <akramer@CERNER.COM> CLIST on Z/OSCLIST on Z/OS (32 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: CLIST on Z/OS (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Call Missing RoutineCall Missing Routine (24 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (66 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (52 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (69 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Call Missing Routine (78 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (109 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (87 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (117 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (57 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Can Proc LP handle OR clauses as constraints?Can Proc LP handle OR clauses as constraints? (26 lines) From: RodrigoLopezAlsina@GMAIL.COM Re: Can Proc LP handle OR clauses as constraints? (36 lines) From: Mark D H Miller <mdhmiller@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (111 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
64-bit SAS with 32-bit catalogs64-bit SAS with 32-bit catalogs (16 lines) From: Wanda Upole <Wanda_Upole@HGSI.COM> Re: 64-bit SAS with 32-bit catalogs (38 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Acronym convergenceAcronym convergence (22 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Acronym convergence (36 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Acronym convergence (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Acronym convergence (43 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Acronym convergence (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Acronym convergence (91 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Acronym convergence (94 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Add user and password details to autoexec file?Re: Add user and password details to autoexec file? (21 lines) From: Shankar <shankar.stat@GMAIL.COM> Aggregating health care claims dataAggregating health care claims data (33 lines) From: Tom Bohman <tmbohman@GMAIL.COM> Re: Aggregating health care claims data (50 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Bad joke Tuesday...Bad joke Tuesday... (23 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Bad joke Tuesday... (44 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Re: Bad joke Tuesday... (33 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Best Practices in changing Char to SAS DATE TIMEBest Practices in changing Char to SAS DATE TIME (31 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Best Practices in changing Char to SAS DATE TIME (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Best Practices in changing Char to SAS DATE TIME (56 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Better integration solution of Web reportBetter integration solution of Web report (52 lines) From: akar <aakarshanabelard@YAHOO.COM> Bivariate Cumulative DistributionBivariate Cumulative Distribution (34 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (39 lines) From: oloolo <dynamicpanel@YAHOO.COM> Bivariate Cumulative Distribution (178 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (186 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (99 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (197 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (218 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (267 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (13 lines) From: Andrew Kramer <akramer@CERNER.COM> CLIST on Z/OSCLIST on Z/OS (32 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: CLIST on Z/OS (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Call Missing RoutineCall Missing Routine (24 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (66 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (52 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (69 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Call Missing Routine (78 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (109 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (87 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (117 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (57 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Can Proc LP handle OR clauses as constraints?Can Proc LP handle OR clauses as constraints? (26 lines) From: RodrigoLopezAlsina@GMAIL.COM Re: Can Proc LP handle OR clauses as constraints? (36 lines) From: Mark D H Miller <mdhmiller@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (111 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Acronym convergenceAcronym convergence (22 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: Acronym convergence (36 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Acronym convergence (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Acronym convergence (43 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Acronym convergence (78 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Acronym convergence (91 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Acronym convergence (94 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Add user and password details to autoexec file?Re: Add user and password details to autoexec file? (21 lines) From: Shankar <shankar.stat@GMAIL.COM> Aggregating health care claims dataAggregating health care claims data (33 lines) From: Tom Bohman <tmbohman@GMAIL.COM> Re: Aggregating health care claims data (50 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Bad joke Tuesday...Bad joke Tuesday... (23 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Bad joke Tuesday... (44 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Re: Bad joke Tuesday... (33 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Best Practices in changing Char to SAS DATE TIMEBest Practices in changing Char to SAS DATE TIME (31 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Best Practices in changing Char to SAS DATE TIME (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Best Practices in changing Char to SAS DATE TIME (56 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Better integration solution of Web reportBetter integration solution of Web report (52 lines) From: akar <aakarshanabelard@YAHOO.COM> Bivariate Cumulative DistributionBivariate Cumulative Distribution (34 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (39 lines) From: oloolo <dynamicpanel@YAHOO.COM> Bivariate Cumulative Distribution (178 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (186 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (99 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (197 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (218 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (267 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (13 lines) From: Andrew Kramer <akramer@CERNER.COM> CLIST on Z/OSCLIST on Z/OS (32 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: CLIST on Z/OS (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Call Missing RoutineCall Missing Routine (24 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (66 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (52 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (69 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Call Missing Routine (78 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (109 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (87 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (117 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (57 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Can Proc LP handle OR clauses as constraints?Can Proc LP handle OR clauses as constraints? (26 lines) From: RodrigoLopezAlsina@GMAIL.COM Re: Can Proc LP handle OR clauses as constraints? (36 lines) From: Mark D H Miller <mdhmiller@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (111 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Add user and password details to autoexec file?Re: Add user and password details to autoexec file? (21 lines) From: Shankar <shankar.stat@GMAIL.COM> Aggregating health care claims dataAggregating health care claims data (33 lines) From: Tom Bohman <tmbohman@GMAIL.COM> Re: Aggregating health care claims data (50 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Bad joke Tuesday...Bad joke Tuesday... (23 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Bad joke Tuesday... (44 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Re: Bad joke Tuesday... (33 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Best Practices in changing Char to SAS DATE TIMEBest Practices in changing Char to SAS DATE TIME (31 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Best Practices in changing Char to SAS DATE TIME (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Best Practices in changing Char to SAS DATE TIME (56 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Better integration solution of Web reportBetter integration solution of Web report (52 lines) From: akar <aakarshanabelard@YAHOO.COM> Bivariate Cumulative DistributionBivariate Cumulative Distribution (34 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (39 lines) From: oloolo <dynamicpanel@YAHOO.COM> Bivariate Cumulative Distribution (178 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (186 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (99 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (197 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (218 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (267 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (13 lines) From: Andrew Kramer <akramer@CERNER.COM> CLIST on Z/OSCLIST on Z/OS (32 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: CLIST on Z/OS (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Call Missing RoutineCall Missing Routine (24 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (66 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (52 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (69 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Call Missing Routine (78 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (109 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (87 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (117 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (57 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Can Proc LP handle OR clauses as constraints?Can Proc LP handle OR clauses as constraints? (26 lines) From: RodrigoLopezAlsina@GMAIL.COM Re: Can Proc LP handle OR clauses as constraints? (36 lines) From: Mark D H Miller <mdhmiller@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (111 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Aggregating health care claims dataAggregating health care claims data (33 lines) From: Tom Bohman <tmbohman@GMAIL.COM> Re: Aggregating health care claims data (50 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Bad joke Tuesday...Bad joke Tuesday... (23 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Bad joke Tuesday... (44 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Re: Bad joke Tuesday... (33 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Best Practices in changing Char to SAS DATE TIMEBest Practices in changing Char to SAS DATE TIME (31 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Best Practices in changing Char to SAS DATE TIME (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Best Practices in changing Char to SAS DATE TIME (56 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Better integration solution of Web reportBetter integration solution of Web report (52 lines) From: akar <aakarshanabelard@YAHOO.COM> Bivariate Cumulative DistributionBivariate Cumulative Distribution (34 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (39 lines) From: oloolo <dynamicpanel@YAHOO.COM> Bivariate Cumulative Distribution (178 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (186 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (99 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (197 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (218 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (267 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (13 lines) From: Andrew Kramer <akramer@CERNER.COM> CLIST on Z/OSCLIST on Z/OS (32 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: CLIST on Z/OS (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Call Missing RoutineCall Missing Routine (24 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (66 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (52 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (69 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Call Missing Routine (78 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (109 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (87 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (117 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (57 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Can Proc LP handle OR clauses as constraints?Can Proc LP handle OR clauses as constraints? (26 lines) From: RodrigoLopezAlsina@GMAIL.COM Re: Can Proc LP handle OR clauses as constraints? (36 lines) From: Mark D H Miller <mdhmiller@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (111 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Bad joke Tuesday...Bad joke Tuesday... (23 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Bad joke Tuesday... (44 lines) From: Phil Rack <PhilRack@MINEQUEST.COM> Re: Bad joke Tuesday... (33 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Best Practices in changing Char to SAS DATE TIMEBest Practices in changing Char to SAS DATE TIME (31 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Best Practices in changing Char to SAS DATE TIME (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Best Practices in changing Char to SAS DATE TIME (56 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Better integration solution of Web reportBetter integration solution of Web report (52 lines) From: akar <aakarshanabelard@YAHOO.COM> Bivariate Cumulative DistributionBivariate Cumulative Distribution (34 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (39 lines) From: oloolo <dynamicpanel@YAHOO.COM> Bivariate Cumulative Distribution (178 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (186 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (99 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (197 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (218 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (267 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (13 lines) From: Andrew Kramer <akramer@CERNER.COM> CLIST on Z/OSCLIST on Z/OS (32 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: CLIST on Z/OS (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Call Missing RoutineCall Missing Routine (24 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (66 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (52 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (69 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Call Missing Routine (78 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (109 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (87 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (117 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (57 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Can Proc LP handle OR clauses as constraints?Can Proc LP handle OR clauses as constraints? (26 lines) From: RodrigoLopezAlsina@GMAIL.COM Re: Can Proc LP handle OR clauses as constraints? (36 lines) From: Mark D H Miller <mdhmiller@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (111 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Best Practices in changing Char to SAS DATE TIMEBest Practices in changing Char to SAS DATE TIME (31 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Best Practices in changing Char to SAS DATE TIME (47 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Best Practices in changing Char to SAS DATE TIME (56 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Better integration solution of Web reportBetter integration solution of Web report (52 lines) From: akar <aakarshanabelard@YAHOO.COM> Bivariate Cumulative DistributionBivariate Cumulative Distribution (34 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (39 lines) From: oloolo <dynamicpanel@YAHOO.COM> Bivariate Cumulative Distribution (178 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (186 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (99 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (197 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (218 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (267 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (13 lines) From: Andrew Kramer <akramer@CERNER.COM> CLIST on Z/OSCLIST on Z/OS (32 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: CLIST on Z/OS (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Call Missing RoutineCall Missing Routine (24 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (66 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (52 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (69 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Call Missing Routine (78 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (109 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (87 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (117 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (57 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Can Proc LP handle OR clauses as constraints?Can Proc LP handle OR clauses as constraints? (26 lines) From: RodrigoLopezAlsina@GMAIL.COM Re: Can Proc LP handle OR clauses as constraints? (36 lines) From: Mark D H Miller <mdhmiller@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (111 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Better integration solution of Web reportBetter integration solution of Web report (52 lines) From: akar <aakarshanabelard@YAHOO.COM> Bivariate Cumulative DistributionBivariate Cumulative Distribution (34 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (39 lines) From: oloolo <dynamicpanel@YAHOO.COM> Bivariate Cumulative Distribution (178 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (186 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (99 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (197 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (218 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (267 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (13 lines) From: Andrew Kramer <akramer@CERNER.COM> CLIST on Z/OSCLIST on Z/OS (32 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: CLIST on Z/OS (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Call Missing RoutineCall Missing Routine (24 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (66 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (52 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (69 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Call Missing Routine (78 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (109 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (87 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (117 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (57 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Can Proc LP handle OR clauses as constraints?Can Proc LP handle OR clauses as constraints? (26 lines) From: RodrigoLopezAlsina@GMAIL.COM Re: Can Proc LP handle OR clauses as constraints? (36 lines) From: Mark D H Miller <mdhmiller@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (111 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Bivariate Cumulative DistributionBivariate Cumulative Distribution (34 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (39 lines) From: oloolo <dynamicpanel@YAHOO.COM> Bivariate Cumulative Distribution (178 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (186 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (99 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (197 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (218 lines) From: Andrew Kramer <akramer@CERNER.COM> Re: Bivariate Cumulative Distribution (267 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Bivariate Cumulative Distribution (13 lines) From: Andrew Kramer <akramer@CERNER.COM> CLIST on Z/OSCLIST on Z/OS (32 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: CLIST on Z/OS (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Call Missing RoutineCall Missing Routine (24 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (66 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (52 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (69 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Call Missing Routine (78 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (109 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (87 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (117 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (57 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Can Proc LP handle OR clauses as constraints?Can Proc LP handle OR clauses as constraints? (26 lines) From: RodrigoLopezAlsina@GMAIL.COM Re: Can Proc LP handle OR clauses as constraints? (36 lines) From: Mark D H Miller <mdhmiller@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (111 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
CLIST on Z/OSCLIST on Z/OS (32 lines) From: Masoud Pajoh <mpajoh@ODOT.ORG> Re: CLIST on Z/OS (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Call Missing RoutineCall Missing Routine (24 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (66 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (52 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (69 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Call Missing Routine (78 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (109 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (87 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (117 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (57 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Can Proc LP handle OR clauses as constraints?Can Proc LP handle OR clauses as constraints? (26 lines) From: RodrigoLopezAlsina@GMAIL.COM Re: Can Proc LP handle OR clauses as constraints? (36 lines) From: Mark D H Miller <mdhmiller@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (111 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Call Missing RoutineCall Missing Routine (24 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (66 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (52 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (69 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Call Missing Routine (78 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (109 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Call Missing Routine (139 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (87 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Call Missing Routine (117 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Call Missing Routine (57 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Call Missing Routine (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Can Proc LP handle OR clauses as constraints?Can Proc LP handle OR clauses as constraints? (26 lines) From: RodrigoLopezAlsina@GMAIL.COM Re: Can Proc LP handle OR clauses as constraints? (36 lines) From: Mark D H Miller <mdhmiller@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (111 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Can Proc LP handle OR clauses as constraints?Can Proc LP handle OR clauses as constraints? (26 lines) From: RodrigoLopezAlsina@GMAIL.COM Re: Can Proc LP handle OR clauses as constraints? (36 lines) From: Mark D H Miller <mdhmiller@GMAIL.COM> Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (111 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Chance to Make SAS-L History: Did You Know That...Re: Chance to Make SAS-L History: Did You Know That... (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Chance to Make SAS-L History: Did You Know That... (111 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Code for Hurdle-NegBin Model in NLMIXEDCode for Hurdle-NegBin Model in NLMIXED (18 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (21 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (37 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (26 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (43 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (95 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (32 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Code for Hurdle-NegBin Model in NLMIXED (36 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Combining an array with a macroCombining an array with a macro (32 lines) From: Marco DiBonaventura <marco.dibonaventura@GMAIL.COM> Re: Combining an array with a macro (52 lines) From: Mary <mlhoward@AVALON.NET> Re: Combining an array with a macro (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Compare id with Retain StatementCompare id with Retain Statement (50 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (77 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (24 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (48 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Compare id with Retain Statement (89 lines) From: Kim Brown <kibrown@LADHS.ORG> Re: Compare id with Retain Statement (103 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Compare id with Retain Statement (142 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Compute sum for rows of dataCompute sum for rows of data (36 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (84 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (108 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (110 lines) From: Huijuan Meng <huijuan_meng@HOTMAIL.COM> Re: Compute sum for rows of data (130 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (155 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (165 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Compute sum for rows of data (153 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Compute sum for rows of data (111 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Confidence interval for failure test dataConfidence interval for failure test data (38 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Re: Confidence interval for failure test data (48 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Confidence interval for failure test data (63 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Confidence interval for failure test data (80 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: Confidence interval for failure test data (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Confidence interval for failure test data (67 lines) From: Susan Durham <sdurham@BIOLOGY.USU.EDU> Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Convert Tsql into sas sql.Convert Tsql into sas sql. (18 lines) From: Jeff <zhujp98@GMAIL.COM> Re: Convert Tsql into sas sql. (28 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Tsql into sas sql. (27 lines) From: T J <tj_noreply@YAHOO.COM> Re: Convert Tsql into sas sql. (25 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Create a report with all duplicate entriesCreate a report with all duplicate entries (107 lines) From: Lizette Koehler <starsoul@MINDSPRING.COM> Re: Create a report with all duplicate entries (150 lines) From: Akshaya <akshaya.nathilvar@GMAIL.COM> Re: Create a report with all duplicate entries (147 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
DDE newbieDDE newbie (25 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Re: DDE newbie (30 lines) From: Lily <debby.gear@GMAIL.COM> Re: DDE newbie (46 lines) From: Bross, Dean S <dean.bross@VA.GOV> Re: DDE newbie (24 lines) From: Gradowsky <marchi.gianluca@LIBERO.IT> Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Data managementData management (35 lines) From: kondal717@GMAIL.COM Re: Data management (104 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Delete cases where the same ids are involved in different orderRe: Delete cases where the same ids are involved in different order (66 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Delete cases where the same ids are involved in different order (105 lines) From: Daniel Santos <dgms@IOL.PT> Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Delete duplicate obsRe: Delete duplicate obs (48 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Did anyone try to import FoxPro .dbf to SAS fileRe: Did anyone try to import FoxPro .dbf to SAS file (20 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Did anyone try to import FoxPro .dbf to SAS file (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Different results with Proc Power and Formula CalculationDifferent results with Proc Power and Formula Calculation (73 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Re: Different results with Proc Power and Formula Calculation (119 lines) From: Robin R High <rhigh@UNMC.EDU> Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Download 100% free flash filesDownload 100% free flash files (21 lines) From: asimhaa@GMAIL.COM Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Efficacy DataEfficacy Data (30 lines) From: Hav <havgalu@GMAIL.COM> Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Excel Crashes When Opening Multi-Sheet TagsetsExcel Crashes When Opening Multi-Sheet Tagsets (15 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (31 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (48 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Andre Wielki <wielki@INED.FR> Re: Excel Crashes When Opening Multi-Sheet Tagsets (64 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: J M <jasonm@UCLA.EDU> Re: Excel Crashes When Opening Multi-Sheet Tagsets (74 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Excel Crashes When Opening Multi-Sheet Tagsets (77 lines) From: Daniel Schuster <daniel.schuster@RCI.COM> Re: Excel Crashes When Opening Multi-Sheet Tagsets (105 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
ExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet TagsetsExcelXP Update? - was: RE: Excel Crashes When Opening Multi-Sheet Tagsets (117 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Extract part of a variableExtract part of a variable (49 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (120 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: Extract part of a variable (85 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (134 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (111 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Extract part of a variable (127 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Extract part of a variable (144 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Extract part of a variable (136 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
FW: Getting the current working directory for the script that is executingFW: Getting the current working directory for the script that is executing (59 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: FW: Getting the current working directory for the script that is executing (73 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
FW: identifiability issuesFW: identifiability issues (640 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> FW: identifiability issues (250 lines) From: Bond, Simon <Simon.Bond@MUNDIPHARMA-RD.EU> Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Fw: HelpFw: Help (55 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Re: Fw: Help (78 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
GUCCI bags ( paypal payment )( www.315store.com )GUCCI bags ( paypal payment )( www.315store.com ) (104 lines) From: jjjjjjjjj <rtiufisfj@SINA.COM> Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Getting the current working directory for the script that isRe: Getting the current working directory for the script that is (77 lines) From: sasuser <olivbernard@GMAIL.COM> Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Getting the current working directory for the script that is executingGetting the current working directory for the script that is executing (61 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
HASUG MEETING ANNOUNCEMENT AND DIRECTIONSHASUG MEETING ANNOUNCEMENT AND DIRECTIONS (87 lines) From: Charles Patridge <charles_s_patridge@PRODIGY.NET> HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
HelpRe: Help (20 lines) From: NOMAIL Roger S. Clark <roger.s.clark@CENSUS.GOV> Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Help with dataRe: Help with data (90 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Help with proc glm urgentHelp with proc glm urgent (74 lines) From: aahan.sas@GMAIL.COM Help with proc glm urgent (67 lines) From: aahan.sas@GMAIL.COM Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Hotelling T^2Hotelling T^2 (16 lines) From: Orin Richards <oowar@YAHOO.COM> Re: Hotelling T^2 (83 lines) From: Robin R High <rhigh@UNMC.EDU> How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
How does PROC MIXED workHow does PROC MIXED work (32 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (37 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (42 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Re: How does PROC MIXED work (48 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (43 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (62 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How does PROC MIXED work (70 lines) From: cylurian <cylurian@GMAIL.COM> Re: How does PROC MIXED work (115 lines) From: Robin R High <rhigh@UNMC.EDU> Re: How does PROC MIXED work (66 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
How to read Nth column in a file using Infile ????How to read Nth column in a file using Infile ???? (31 lines) From: pinu <amarmundankar@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (39 lines) From: karma <dorjetarap@GOOGLEMAIL.COM> Re: How to read Nth column in a file using Infile ???? (57 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (46 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: How to read Nth column in a file using Infile ???? (54 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: How to read Nth column in a file using Infile ???? (44 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
How would you advertise your career to a bunch of ten-year olds?How would you advertise your career to a bunch of ten-year olds? (23 lines) From: Stefan Osborne <zonkerbrainless@YAHOO.COM> Re: How would you advertise your career to a bunch of ten-year olds? (92 lines) From: Teed, Lionel <Lionel.Teed@TD.COM> Re: How would you advertise your career to a bunch of ten-year olds? (49 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How would you advertise your career to a bunch of ten-year olds? (41 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How would you advertise your career to a bunch of ten-year olds? (43 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Re: How would you advertise your career to a bunch of ten-year olds? (60 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How would you advertise your career to a bunch of ten-year olds? (105 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: How would you advertise your career to a bunch of ten-year olds? (54 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How would you advertise your career to a bunch of ten-year olds? (125 lines) From: Mary <mlhoward@AVALON.NET> If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
If, then statementsIf, then statements (53 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (133 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (150 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (179 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (82 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: If, then statements (86 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (118 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: If, then statements (132 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: If, then statements (33 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: If, then statements (252 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: If, then statements (328 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> Re: If, then statements (354 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Intrareader variability using SASRe: Intrareader variability using SAS (87 lines) From: Reed, Derek <derek.reed@SINCLAIR.EDU> Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Intrareader variablity using SASIntrareader variablity using SAS (53 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Intrareader variablity using SAS (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Is there a way to detect if an ODS destination is being used?Is there a way to detect if an ODS destination is being used? (16 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Is there a way to detect if an ODS destination is being used? (21 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there a way to detect if an ODS destination is being used? (36 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Keep dataset labelKeep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Keep dataset label (9 lines) From: Felicia Franzen <Felicia.Franzen@QUINTILES.COM> Re: Keep dataset label (35 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Keeping Unique ObsRe: Keeping Unique Obs (37 lines) From: kondal717@GMAIL.COM Re: Keeping Unique Obs (99 lines) From: N, Raghupathi <raghupathi.n@GENPACT.COM> Re: Keeping Unique Obs (107 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
LSMEANS oddityLSMEANS oddity (68 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (155 lines) From: Robin R High <rhigh@UNMC.EDU> Re: LSMEANS oddity (113 lines) From: Jay Weedon <jweedon@EARTHLINK.NET> Re: LSMEANS oddity (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: LSMEANS oddity (150 lines) From: Hixon, John <jhixon@AMGEN.COM> Re: LSMEANS oddity (212 lines) From: Hixon, John <jhixon@AMGEN.COM> Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Linear Optimization (Proc LP) with OR constraintLinear Optimization (Proc LP) with OR constraint (21 lines) From: Paul Walker <walker.627@OSU.EDU> Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Looking Backward and Forward in a Data StepLooking Backward and Forward in a Data Step (102 lines) From: Deborah Testa <dtesta@SEVENOFNINESYSTEMS.COM> Re: Looking Backward and Forward in a Data Step (115 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Looking Backward and Forward in a Data Step (121 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (133 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Looking Backward and Forward in a Data Step (207 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Looking Backward and Forward in a Data Step (120 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Looking Backward and Forward in a Data Step (169 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Looking Backward and Forward in a Data Step (190 lines) From: Andre Wielki <wielki@INED.FR> Re: Looking Backward and Forward in a Data Step (268 lines) From: oloolo <dynamicpanel@YAHOO.COM> MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
MLE & weibull probability distributionMLE & weibull probability distribution (17 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (35 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: MLE & weibull probability distribution (52 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (47 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Re: MLE & weibull probability distribution (82 lines) From: Robin R High <rhigh@UNMC.EDU> Re: MLE & weibull probability distribution (61 lines) From: Jeff <jeffrey.m.allard@GMAIL.COM> Re: MLE & weibull probability distribution (69 lines) From: Rob Rob <robinson.inj@GMAIL.COM> Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Macro Variable in File NamesMacro Variable in File Names (19 lines) From: J M <jasonm@UCLA.EDU> Re: Macro Variable in File Names (27 lines) From: Daniel Santos <dgms@IOL.PT> Re: Macro Variable in File Names (38 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Mean Time to Event??Mean Time to Event?? (20 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (22 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Mean Time to Event?? (48 lines) From: Bminer <b_miner@LIVE.COM> Re: Mean Time to Event?? (66 lines) From: Bminer <b_miner@LIVE.COM> Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Numeric Precision Issue with Summed Field from PROC SUMMARY?Numeric Precision Issue with Summed Field from PROC SUMMARY? (127 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (138 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (86 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (150 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (207 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (241 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (266 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (270 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (309 lines) From: Søren Lassen <s.lassen@POST.TELE.DK> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (166 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (69 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (191 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (359 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (52 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (101 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (128 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (130 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (244 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (171 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (218 lines) From: Mary <mlhoward@AVALON.NET> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (217 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Numeric Precision Issue with Summed Field from PROC SUMMARY? (245 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
OT- rise of spam ?Re: OT- rise of spam ? (24 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: OT- rise of spam ? (51 lines) From: Andre Wielki <wielki@INED.FR> OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
OT: How would you advertise your career to a bunch of ten-year olds?OT: How would you advertise your career to a bunch of ten-year olds? (83 lines) From: Choate, Paul@DDS <pchoate@DDS.CA.GOV> Re: OT: How would you advertise your career to a bunch of ten-year olds? (93 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
OT: Tuesday PuzzleOT: Tuesday Puzzle (30 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (39 lines) From: FPAStatman <brentvtimothy@GMAIL.COM> Re: OT: Tuesday Puzzle (90 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: OT: Tuesday Puzzle (45 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (91 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: OT: Tuesday Puzzle (133 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: OT: Tuesday Puzzle (71 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (90 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: OT: Tuesday Puzzle (86 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (101 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: OT: Tuesday Puzzle (51 lines) From: Daniel Nordlund <djnordlund@VERIZON.NET> Re: OT: Tuesday Puzzle (83 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
OT: pass a value to SAS Connect sessionOT: pass a value to SAS Connect session (36 lines) From: Gordon Cox <gordon.cox@GMAIL.COM> Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Ocean technologiesOcean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Ocean technologies (43 lines) From: vijay <vijay.oceantech@GMAIL.COM> Re: Ocean technologies (45 lines) From: Kenneth M. Lin <kenneth_m_lin@SBCGLOBAL.NET> Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Online SAS Training Seminars April 28, 29 and 30Online SAS Training Seminars April 28, 29 and 30 (33 lines) From: Andrew Karp, Sierra Info Services <sfbay0001@AOL.COM> Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Openings for Mainframe at MN with Pacbase expOpenings for Mainframe at MN with Pacbase exp (54 lines) From: Aniket <amittal9186@GMAIL.COM> PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
PARSING SAS LOG for errorsPARSING SAS LOG for errors (61 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (64 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (78 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (91 lines) From: SS <shamindra.shrotriya@GMAIL.COM> Re: PARSING SAS LOG for errors (110 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PARSING SAS LOG for errors (167 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: PARSING SAS LOG for errors (118 lines) From: Savian <savian.net@GMAIL.COM> Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Parsing SAS Log for errorsParsing SAS Log for errors (84 lines) From: Phil Busby <fransioli@HOTMAIL.COM> Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Post hoc tests with proc glm and covariatesRe: Post hoc tests with proc glm and covariates (56 lines) From: Bminer <b_miner@LIVE.COM> Re: Post hoc tests with proc glm and covariates (68 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Problem with reading in a listing fileProblem with reading in a listing file (20 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (50 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (37 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (105 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Problem with reading in a listing file (97 lines) From: ./ ADD NAME=Data _null_; <iebupdte@GMAIL.COM> Re: Problem with reading in a listing file (53 lines) From: Kevin Y <kevin77711@YAHOO.COM> Re: Problem with reading in a listing file (47 lines) From: Kevin Y <kevin77711@YAHOO.COM> Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Problem with scan functionProblem with scan function (43 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Re: Problem with scan function (77 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Problem with scan function (101 lines) From: Bo Zhang <finzhang2000@GMAIL.COM> Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Proc GCHART issueProc GCHART issue (39 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (45 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc GCHART issue (60 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (78 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Re: Proc GCHART issue (157 lines) From: Mike Zdeb <msz03@ALBANY.EDU> Re: Proc GCHART issue (159 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Proc Mixed and Covariance StructureProc Mixed and Covariance Structure (45 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Re: Proc Mixed and Covariance Structure (113 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Proc Mixed and Covariance Structure (122 lines) From: sudip chatterjee <sudip.memphis@GMAIL.COM> Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Proc Tabulate Var Font_sizeProc Tabulate Var Font_size (27 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate Var Font_size (39 lines) From: Richard <rdevenezia@WILDBLUE.NET> Re: Proc Tabulate Var Font_size (50 lines) From: J M <jasonm@UCLA.EDU> Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Proc Tabulate and TagatterProc Tabulate and Tagatter (20 lines) From: J M <jasonm@UCLA.EDU> Re: Proc Tabulate and Tagatter (36 lines) From: J M <jasonm@UCLA.EDU> Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Proc tabulate issue The real solutionRe: Proc tabulate issue The real solution (132 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Proc tabulate problemProc tabulate problem (23 lines) From: chumba <vikas.dharamsattu@GMAIL.COM> Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Purse IndexPurse Index (107 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (149 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Purse Index (169 lines) From: Michael Bryce Herrington <mherrin@G.CLEMSON.EDU> Re: Purse Index (137 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: Purse Index (63 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Read the compressed (abc.sas7bdat.Z) SAS dataset directlyRead the compressed (abc.sas7bdat.Z) SAS dataset directly (21 lines) From: Kunal Kelkar <mailtokunalkelkar@GMAIL.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (40 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (58 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (92 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Read the compressed (abc.sas7bdat.Z) SAS dataset directly (107 lines) From: Rivo Ramamonjy <rivo.ramamonjy@TRICAST-GROUP.COM> Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Reg: Proc mixed codeRe: Reg: Proc mixed code (25 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (40 lines) From: srinathrao.sas@GMAIL.COM Re: Reg: Proc mixed code (28 lines) From: Shankar <shankar.stat@GMAIL.COM> Re: Reg: Proc mixed code (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Reg: Proc mixed code (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Regression tree in SAS?Regression tree in SAS? (15 lines) From: hua gang <hg448@YAHOO.COM> Regression tree in SAS? (18 lines) From: Simon, Lorna <Lorna.Simon@UMASSMED.EDU> Re: Regression tree in SAS? (41 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (33 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Re: Regression tree in SAS? (29 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Regression tree in SAS? (53 lines) From: Murphy Choy <goladin@GMAIL.COM> Re: Regression tree in SAS? (69 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Reliability question for the reliability expert or the proc mixed expertRe: Reliability question for the reliability expert or the proc mixed expert (66 lines) From: Sinco, Brandy <brsinco@UMICH.EDU> Reliability question for the reliability expert or the proc mixed expert.
Reliability question for the reliability expert or the proc mixed expert.