"R" the end of SAS?"R" the end of SAS? (34 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: "R" the end of SAS? (108 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: "R" the end of SAS? (18 lines) From: Stanley A. Gorodenski <vvgsgor@DE.STATE.AZ.US> Re: "R" the end of SAS? (46 lines) From: Peter Flom <peter.flom@NDRI.ORG> Re: "R" the end of SAS? (80 lines) From: Matthew Sheffer <msheffer@SPEAKEASY.NET> Re: "R" the end of SAS? (65 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: "R" the end of SAS? (42 lines) From: Peter Flom <peter.flom@NDRI.ORG> Re: "R" the end of SAS? (83 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: "R" the end of SAS? (77 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: "R" the end of SAS? (18 lines) From: Stig Eide <stigeide@YAHOO.COM> -2LL v Wald v Score in PHREG small samples-2LL v Wald v Score in PHREG small samples (29 lines) From: Jacqueline R Cater <jcater@HOME.COM> Re: -2LL v Wald v Score in PHREG small samples (36 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> <No subject><No subject> (8 lines) From: F.J. Kelley <jkelley@ARCHES.UGA.EDU> ???character array??????character array??? (42 lines) From: Helen li <qunli2001@YAHOO.COM> Re: ???character array??? (70 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: ???character array??? (41 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: ???character array??? (166 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> A general request re Statistical ProblemsA general request re Statistical Problems (22 lines) From: Peter Flom <peter.flom@NDRI.ORG> Re: A general request re Statistical Problems (45 lines) From: Thompson Bill T Contr USAFSAM/FEC <Bill.Thompson@BROOKS.AF.MIL> AW: filename statement on the mainframeAW: filename statement on the mainframe (54 lines) From: Bernd Bausch <bernd.bausch@HEIDELBERG.CS2-INFORMATIK.DE> AW: sas datesAW: sas dates (78 lines) From: Eckhardt, Michael <Michael.Eckhardt@T-SYSTEMS.DE> Antwort: Re: IF StatementAntwort: Re: IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> ApologiesApologies (20 lines) From: Peter Flom <peter.flom@NDRI.ORG> Associate, Insurance Acturary Position/Florida RelocationAssociate, Insurance Acturary Position/Florida Relocation (36 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Better way to rename many variables?Re: Better way to rename many variables? (24 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAMS> Re: Better way to rename many variables? (19 lines) From: Stanley A. Gorodenski <vvgsgor@DE.STATE.AZ.US> Biostatistician / Research Associate, Job Posting, Bay Area, CABiostatistician / Research Associate, Job Posting, Bay Area, CA (32 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> Biostatistician, Job Posting, Bay Area, CABiostatistician, Job Posting, Bay Area, CA (44 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
-2LL v Wald v Score in PHREG small samples-2LL v Wald v Score in PHREG small samples (29 lines) From: Jacqueline R Cater <jcater@HOME.COM> Re: -2LL v Wald v Score in PHREG small samples (36 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> <No subject><No subject> (8 lines) From: F.J. Kelley <jkelley@ARCHES.UGA.EDU> ???character array??????character array??? (42 lines) From: Helen li <qunli2001@YAHOO.COM> Re: ???character array??? (70 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: ???character array??? (41 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: ???character array??? (166 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> A general request re Statistical ProblemsA general request re Statistical Problems (22 lines) From: Peter Flom <peter.flom@NDRI.ORG> Re: A general request re Statistical Problems (45 lines) From: Thompson Bill T Contr USAFSAM/FEC <Bill.Thompson@BROOKS.AF.MIL> AW: filename statement on the mainframeAW: filename statement on the mainframe (54 lines) From: Bernd Bausch <bernd.bausch@HEIDELBERG.CS2-INFORMATIK.DE> AW: sas datesAW: sas dates (78 lines) From: Eckhardt, Michael <Michael.Eckhardt@T-SYSTEMS.DE> Antwort: Re: IF StatementAntwort: Re: IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> ApologiesApologies (20 lines) From: Peter Flom <peter.flom@NDRI.ORG> Associate, Insurance Acturary Position/Florida RelocationAssociate, Insurance Acturary Position/Florida Relocation (36 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Better way to rename many variables?Re: Better way to rename many variables? (24 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAMS> Re: Better way to rename many variables? (19 lines) From: Stanley A. Gorodenski <vvgsgor@DE.STATE.AZ.US> Biostatistician / Research Associate, Job Posting, Bay Area, CABiostatistician / Research Associate, Job Posting, Bay Area, CA (32 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> Biostatistician, Job Posting, Bay Area, CABiostatistician, Job Posting, Bay Area, CA (44 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
<No subject><No subject> (8 lines) From: F.J. Kelley <jkelley@ARCHES.UGA.EDU> ???character array??????character array??? (42 lines) From: Helen li <qunli2001@YAHOO.COM> Re: ???character array??? (70 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: ???character array??? (41 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: ???character array??? (166 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> A general request re Statistical ProblemsA general request re Statistical Problems (22 lines) From: Peter Flom <peter.flom@NDRI.ORG> Re: A general request re Statistical Problems (45 lines) From: Thompson Bill T Contr USAFSAM/FEC <Bill.Thompson@BROOKS.AF.MIL> AW: filename statement on the mainframeAW: filename statement on the mainframe (54 lines) From: Bernd Bausch <bernd.bausch@HEIDELBERG.CS2-INFORMATIK.DE> AW: sas datesAW: sas dates (78 lines) From: Eckhardt, Michael <Michael.Eckhardt@T-SYSTEMS.DE> Antwort: Re: IF StatementAntwort: Re: IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> ApologiesApologies (20 lines) From: Peter Flom <peter.flom@NDRI.ORG> Associate, Insurance Acturary Position/Florida RelocationAssociate, Insurance Acturary Position/Florida Relocation (36 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Better way to rename many variables?Re: Better way to rename many variables? (24 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAMS> Re: Better way to rename many variables? (19 lines) From: Stanley A. Gorodenski <vvgsgor@DE.STATE.AZ.US> Biostatistician / Research Associate, Job Posting, Bay Area, CABiostatistician / Research Associate, Job Posting, Bay Area, CA (32 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> Biostatistician, Job Posting, Bay Area, CABiostatistician, Job Posting, Bay Area, CA (44 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
???character array??????character array??? (42 lines) From: Helen li <qunli2001@YAHOO.COM> Re: ???character array??? (70 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: ???character array??? (41 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: ???character array??? (166 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> A general request re Statistical ProblemsA general request re Statistical Problems (22 lines) From: Peter Flom <peter.flom@NDRI.ORG> Re: A general request re Statistical Problems (45 lines) From: Thompson Bill T Contr USAFSAM/FEC <Bill.Thompson@BROOKS.AF.MIL> AW: filename statement on the mainframeAW: filename statement on the mainframe (54 lines) From: Bernd Bausch <bernd.bausch@HEIDELBERG.CS2-INFORMATIK.DE> AW: sas datesAW: sas dates (78 lines) From: Eckhardt, Michael <Michael.Eckhardt@T-SYSTEMS.DE> Antwort: Re: IF StatementAntwort: Re: IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> ApologiesApologies (20 lines) From: Peter Flom <peter.flom@NDRI.ORG> Associate, Insurance Acturary Position/Florida RelocationAssociate, Insurance Acturary Position/Florida Relocation (36 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Better way to rename many variables?Re: Better way to rename many variables? (24 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAMS> Re: Better way to rename many variables? (19 lines) From: Stanley A. Gorodenski <vvgsgor@DE.STATE.AZ.US> Biostatistician / Research Associate, Job Posting, Bay Area, CABiostatistician / Research Associate, Job Posting, Bay Area, CA (32 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> Biostatistician, Job Posting, Bay Area, CABiostatistician, Job Posting, Bay Area, CA (44 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
A general request re Statistical ProblemsA general request re Statistical Problems (22 lines) From: Peter Flom <peter.flom@NDRI.ORG> Re: A general request re Statistical Problems (45 lines) From: Thompson Bill T Contr USAFSAM/FEC <Bill.Thompson@BROOKS.AF.MIL> AW: filename statement on the mainframeAW: filename statement on the mainframe (54 lines) From: Bernd Bausch <bernd.bausch@HEIDELBERG.CS2-INFORMATIK.DE> AW: sas datesAW: sas dates (78 lines) From: Eckhardt, Michael <Michael.Eckhardt@T-SYSTEMS.DE> Antwort: Re: IF StatementAntwort: Re: IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> ApologiesApologies (20 lines) From: Peter Flom <peter.flom@NDRI.ORG> Associate, Insurance Acturary Position/Florida RelocationAssociate, Insurance Acturary Position/Florida Relocation (36 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Better way to rename many variables?Re: Better way to rename many variables? (24 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAMS> Re: Better way to rename many variables? (19 lines) From: Stanley A. Gorodenski <vvgsgor@DE.STATE.AZ.US> Biostatistician / Research Associate, Job Posting, Bay Area, CABiostatistician / Research Associate, Job Posting, Bay Area, CA (32 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> Biostatistician, Job Posting, Bay Area, CABiostatistician, Job Posting, Bay Area, CA (44 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
AW: filename statement on the mainframeAW: filename statement on the mainframe (54 lines) From: Bernd Bausch <bernd.bausch@HEIDELBERG.CS2-INFORMATIK.DE> AW: sas datesAW: sas dates (78 lines) From: Eckhardt, Michael <Michael.Eckhardt@T-SYSTEMS.DE> Antwort: Re: IF StatementAntwort: Re: IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> ApologiesApologies (20 lines) From: Peter Flom <peter.flom@NDRI.ORG> Associate, Insurance Acturary Position/Florida RelocationAssociate, Insurance Acturary Position/Florida Relocation (36 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Better way to rename many variables?Re: Better way to rename many variables? (24 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAMS> Re: Better way to rename many variables? (19 lines) From: Stanley A. Gorodenski <vvgsgor@DE.STATE.AZ.US> Biostatistician / Research Associate, Job Posting, Bay Area, CABiostatistician / Research Associate, Job Posting, Bay Area, CA (32 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> Biostatistician, Job Posting, Bay Area, CABiostatistician, Job Posting, Bay Area, CA (44 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
AW: sas datesAW: sas dates (78 lines) From: Eckhardt, Michael <Michael.Eckhardt@T-SYSTEMS.DE> Antwort: Re: IF StatementAntwort: Re: IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> ApologiesApologies (20 lines) From: Peter Flom <peter.flom@NDRI.ORG> Associate, Insurance Acturary Position/Florida RelocationAssociate, Insurance Acturary Position/Florida Relocation (36 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Better way to rename many variables?Re: Better way to rename many variables? (24 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAMS> Re: Better way to rename many variables? (19 lines) From: Stanley A. Gorodenski <vvgsgor@DE.STATE.AZ.US> Biostatistician / Research Associate, Job Posting, Bay Area, CABiostatistician / Research Associate, Job Posting, Bay Area, CA (32 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> Biostatistician, Job Posting, Bay Area, CABiostatistician, Job Posting, Bay Area, CA (44 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Antwort: Re: IF StatementAntwort: Re: IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> ApologiesApologies (20 lines) From: Peter Flom <peter.flom@NDRI.ORG> Associate, Insurance Acturary Position/Florida RelocationAssociate, Insurance Acturary Position/Florida Relocation (36 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Better way to rename many variables?Re: Better way to rename many variables? (24 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAMS> Re: Better way to rename many variables? (19 lines) From: Stanley A. Gorodenski <vvgsgor@DE.STATE.AZ.US> Biostatistician / Research Associate, Job Posting, Bay Area, CABiostatistician / Research Associate, Job Posting, Bay Area, CA (32 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> Biostatistician, Job Posting, Bay Area, CABiostatistician, Job Posting, Bay Area, CA (44 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
ApologiesApologies (20 lines) From: Peter Flom <peter.flom@NDRI.ORG> Associate, Insurance Acturary Position/Florida RelocationAssociate, Insurance Acturary Position/Florida Relocation (36 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Better way to rename many variables?Re: Better way to rename many variables? (24 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAMS> Re: Better way to rename many variables? (19 lines) From: Stanley A. Gorodenski <vvgsgor@DE.STATE.AZ.US> Biostatistician / Research Associate, Job Posting, Bay Area, CABiostatistician / Research Associate, Job Posting, Bay Area, CA (32 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> Biostatistician, Job Posting, Bay Area, CABiostatistician, Job Posting, Bay Area, CA (44 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Associate, Insurance Acturary Position/Florida RelocationAssociate, Insurance Acturary Position/Florida Relocation (36 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Better way to rename many variables?Re: Better way to rename many variables? (24 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAMS> Re: Better way to rename many variables? (19 lines) From: Stanley A. Gorodenski <vvgsgor@DE.STATE.AZ.US> Biostatistician / Research Associate, Job Posting, Bay Area, CABiostatistician / Research Associate, Job Posting, Bay Area, CA (32 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> Biostatistician, Job Posting, Bay Area, CABiostatistician, Job Posting, Bay Area, CA (44 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Better way to rename many variables?Re: Better way to rename many variables? (24 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAMS> Re: Better way to rename many variables? (19 lines) From: Stanley A. Gorodenski <vvgsgor@DE.STATE.AZ.US> Biostatistician / Research Associate, Job Posting, Bay Area, CABiostatistician / Research Associate, Job Posting, Bay Area, CA (32 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> Biostatistician, Job Posting, Bay Area, CABiostatistician, Job Posting, Bay Area, CA (44 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Biostatistician / Research Associate, Job Posting, Bay Area, CABiostatistician / Research Associate, Job Posting, Bay Area, CA (32 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> Biostatistician, Job Posting, Bay Area, CABiostatistician, Job Posting, Bay Area, CA (44 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Biostatistician, Job Posting, Bay Area, CABiostatistician, Job Posting, Bay Area, CA (44 lines) From: Tom Whiting <t.whiting@WORLDNET.ATT.NET> CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250CNF: QWE2002 -- March 2002, Brussels: Register Now and Save $250 (105 lines) From: SR <info@SOFT.COM> Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Certificate ExamCertificate Exam (37 lines) From: fangfang qin <joshqin@MSN.COM> Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Chart variable order using PROC GCHARTRe: Chart variable order using PROC GCHART (83 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Chart variable order using PROC GCHART (115 lines) From: Don Henderson <don.henderson@US.PWCGLOBAL.COM> Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Checking Status of SAS-L listChecking Status of SAS-L list (21 lines) From: Paul Nicholson <eclpn@LUCS-01.NOVELL.LEEDS.AC.UK> Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Clinical Programmer / Kent and SwitzerlandClinical Programmer / Kent and Switzerland (28 lines) From: Tina Punter <tpunter@MIND.CO.UK> Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Collaboration OfferCollaboration Offer (68 lines) From: Business Guarantee <info@BSNGUARANTEE.COM> Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Conditional running of a MacroConditional running of a Macro (80 lines) From: Krone, Ben --- Manager - Operations Systems --- GO <Ben.Krone@AF.COM> Re: Conditional running of a Macro (166 lines) From: David L. Ward <dward@SASHELP.COM> Re: Conditional running of a Macro (131 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Conditional running of a Macro (122 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Conditional running of a Macro (40 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (154 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Conditional running of a Macro (59 lines) From: kviel <kviel@GMCF.ORG> Re: Conditional running of a Macro (134 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Conditional running of a Macro (13 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Contour linesContour lines (27 lines) From: Armin Gemperli <Armin.Gemperli@UNIBAS.CH> Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Count char var with wildcards (was Frequencies given Conditio ns on Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (109 lines) From: Droogendyk, Harry <Harry.Droogendyk@CIBC.COM> Re: Count char var with wildcards (was Frequencies given Conditio ns on Char Variable) (120 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Count char var with wildcards (was Frequencies given Conditio nson Char Variable)Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (160 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (28 lines) From: Quentin McMullen <QuentinMcMullen@WESTAT.COM> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (60 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Count char var with wildcards (was Frequencies given Conditio nson Char Variable) (70 lines) From: howard_schreier@ITA.DOC.GOV Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Count char var with wildcards (was Frequencies given Conditions on Char Variable)Count char var with wildcards (was Frequencies given Conditions on Char Variable) (79 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Define the size of array?Define the size of array? (62 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Define the size of array? (99 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Define the size of array? (158 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Define the size of array? (47 lines) From: Jens Ulrik Jacobsen <zvi1asefu8001@SNEAKEMAIL.COM> Re: Define the size of array? (64 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Define the size of array? (31 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Define the size of array? (53 lines) From: kviel <kviel@GMCF.ORG> Re: Define the size of array? (136 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Driving distance between A and B.Driving distance between A and B. (20 lines) From: Jack Shostak <shost001@MC.DUKE.EDU> Re: Driving distance between A and B. (35 lines) From: Schechter, Robert S <robert.schechter@ASTRAZENECA.COM> Re: Driving distance between A and B. (30 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Efficiency (Was RE: Identifying overlapping groups)Efficiency (Was RE: Identifying overlapping groups) (42 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (86 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (74 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (77 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Efficiency (Was RE: Identifying overlapping groups) (28 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Email Etiquette ^2Email Etiquette ^2 (17 lines) From: Fernando Colina <Fernando.Colina@UMB.EDU> Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Error Messages When Converting a SAS JMP File to an Excel SpreadsheetError Messages When Converting a SAS JMP File to an Excel Spreadsheet (20 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Excel ImportRe: Excel Import (201 lines) From: Paul Choate <pchoate@JPS.NET> Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Experimental DesignExperimental Design (25 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Experimental Design (45 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
FORM TYPE=TEXT problemFORM TYPE=TEXT problem (29 lines) From: Action Man <wollo_desse@HOTMAIL.COM> FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
FW: Update a flatfile "in place"?FW: Update a flatfile "in place"? (120 lines) From: David L. Ward <dward@SASHELP.COM> Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Final totals...Final totals... (62 lines) From: TIEDENS GARY (smg1get) <smg1get@UPS.COM> Final totals... (118 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Final totals... (43 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Flat file convert to PDF and emailFlat file convert to PDF and email (66 lines) From: bracyr <bracyrspam@YAHOO.COM> Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Frequencies given Conditions on Char VariableFrequencies given Conditions on Char Variable (58 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Frequencies given Conditions on Char Variable (93 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Frequencies given Conditions on Char Variable (22 lines) From: Mark Moran <mark.k.moran@CENSUS.GOV> Re: Frequencies given Conditions on Char Variable (74 lines) From: Brian Shilling <brian.shilling@BMS.COM> Re: Frequencies given Conditions on Char Variable (49 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Frequencies given Conditions on Char Variable (42 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Function for later observationsFunction for later observations (18 lines) From: lance freeman <tyroc7@HOTMAIL.COM> Re: Function for later observations (73 lines) From: bramley.m@PG.COM Re: Function for later observations (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Function for later observations (66 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Function for later observations (577 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Function for later observations (32 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Re: Function for later observations (292 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Function for later observations (314 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Fw: "R" the end of SASFw: "R" the end of SAS (175 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! ---GET THE BEST INTERNET EXPOSURE---DO MASS E-MAIL AND GET RESULTS!!! --- (20 lines) From: flaysatiu7@FLASHMAIL.COM Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Hazard ratioHazard ratio (51 lines) From: Gray, Alex M <amg5818@GLAXOWELLCOME.COM> Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Help with ANCOVA adjusted meansHelp with ANCOVA adjusted means (29 lines) From: Disco Stu <discostu1117@YAHOO.COM> Re: Help with ANCOVA adjusted means (37 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: Help with ANCOVA adjusted means (49 lines) From: Paul R Swank <Paul.R.Swank@UTH.TMC.EDU> Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Help with _GET_TEXT_ method in CALL NOTIFY please!Help with _GET_TEXT_ method in CALL NOTIFY please! (42 lines) From: adil <adil@MATH.NSC.RU> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (57 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (83 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (85 lines) From: Simon Pickles <simon.pickles@BARCAP.COM> Re: Help with _GET_TEXT_ method in CALL NOTIFY please! (189 lines) From: David L. Ward <dward@SASHELP.COM> Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Help, Running Batch/ Multiple SAS Prgms...Help, Running Batch/ Multiple SAS Prgms... (23 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (44 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (27 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Help, Running Batch/ Multiple SAS Prgms... (35 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Help, Running Batch/ Multiple SAS Prgms... (37 lines) From: James Green <james.green@ALCATEL.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (43 lines) From: Fehd, Ronald J. <rjf2@CDC.GOV> Re: Help, Running Batch/ Multiple SAS Prgms... (53 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: Help, Running Batch/ Multiple SAS Prgms... (80 lines) From: Louis Broekhuijsen-Bl鰕s <louis.broekhuijsen-bloys@CMG.NL> Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Here's one for the Cube gurus...Here's one for the Cube gurus... (69 lines) From: Pat Flickner <p_flick@YAHOO.COM> Re: Here's one for the Cube gurus... (83 lines) From: Paul Choate <pchoate@JPS.NET> Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Hierarchical Stepwise Logistic RegressionRe: Hierarchical Stepwise Logistic Regression (36 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Hierarchical Stepwise Logistic Regression (28 lines) From: Carole Lunney <carole@ISP01.NET> Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Holiday SAS fun WAS: function practice from years backHoliday SAS fun WAS: function practice from years back (64 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (85 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Holiday SAS fun WAS: function practice from years back (78 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (101 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (98 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (30 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (22 lines) From: David L. Ward <dward@SASHELP.COM> Re: Holiday SAS fun WAS: function practice from years back (49 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Holiday SAS fun WAS: function practice from years back (32 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
How to kill Batch Processes in NT?How to kill Batch Processes in NT? (14 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to kill Batch Processes in NT? (20 lines) From: clmakinson@GOODYEAR.COM Re: How to kill Batch Processes in NT? (32 lines) From: Stig Eide <stigeide@YAHOO.COM> How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
How to tracking running error happened in SAS' macro programHow to tracking running error happened in SAS' macro program (13 lines) From: Lu Jinhai <lujh888@263.NET> Re: How to tracking running error happened in SAS' macro program (24 lines) From: Paul Choate <pchoate@JPS.NET> Re: How to tracking running error happened in SAS' macro program (28 lines) From: Stig Eide <stigeide@YAHOO.COM> Re: How to tracking running error happened in SAS' macro program (38 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: How to tracking running error happened in SAS' macro program (76 lines) From: bramley.m@PG.COM IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
IF StatementIF Statement (21 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (32 lines) From: Soumen Mukherjee <SMukherjee@MAPSNET.COM> Re: IF Statement (58 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: IF Statement (49 lines) From: David L. Ward <dward@SASHELP.COM> IF Statement (74 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: IF Statement (42 lines) From: Ace <b.rogers@VIRGIN.NET> Re: IF Statement (25 lines) From: David L. Ward <dward@SASHELP.COM> Re: IF Statement (56 lines) From: Abakah Nori (crm1nxa) <crm1nxa@UPS.COM> Re: IF Statement (153 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (207 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (82 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: IF Statement (307 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (274 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (100 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: IF Statement (448 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (162 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: IF Statement (49 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: IF Statement (71 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
INTNX and changing the day of the weekINTNX and changing the day of the week (8 lines) From: Jenine Eason <jenine.eason@AUTOTRADER.COM> Re: INTNX and changing the day of the week (34 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: INTNX and changing the day of the week (51 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: INTNX and changing the day of the week (84 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Identifying overlapping groupsIdentifying overlapping groups (51 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Re: Identifying overlapping groups (143 lines) From: Huang, Ya <ya.huang@PFIZER.COM> Re: Identifying overlapping groups (84 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Identifying subscribed serverIdentifying subscribed server (38 lines) From: <Frank Mwaniki> <frank.mwaniki@PHARMA.NOVARTIS.COM> Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Initial values in NLPNRAInitial values in NLPNRA (12 lines) From: Sonia Laszlo <slaszlo@RYERSON.CA> Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Keeping a variable in proc means or porc summaryKeeping a variable in proc means or porc summary (8 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in proc means or porc summary (16 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Keeping a variable in the output file in proc means or proc s ummaryRe: Keeping a variable in the output file in proc means or proc s ummary (38 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Keeping a variable in the output file in proc means or proc summaryKeeping a variable in the output file in proc means or proc summary (9 lines) From: Dan Lu <z.lu@ATT.NET> Re: Keeping a variable in the output file in proc means or proc summary (13 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Re: Keeping a variable in the output file in proc means or proc summary (48 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> Re: Keeping a variable in the output file in proc means or proc summary (18 lines) From: Tim Lawson <tlawson@XTRA.CO.NZ> Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Keeping a variable in the output file in proc means or procsu mmaryRe: Keeping a variable in the output file in proc means or procsu mmary (50 lines) From: Paul.Dorfman bcbsfl.com <Paul.Dorfman@BCBSFL.COM> Re: Keeping a variable in the output file in proc means or procsu mmary (83 lines) From: Richard Simhon <Richard.Simhon@CORNHILL.CO.UK> Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Keeping a variable in the output file in proc means or procsummaryRe: Keeping a variable in the output file in proc means or procsummary (94 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Keeping a variable in the output file in proc means orprocsummaryRe: Keeping a variable in the output file in proc means orprocsummary (158 lines) From: Rob Rohrbough <Rob@ROHRBOUGH-SYSTEMS.COM> LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
LEADING QUOTES IN EXCELLEADING QUOTES IN EXCEL (23 lines) From: Dirk Cosijn <dirk.cosijn@PANDORA.BE> Re: LEADING QUOTES IN EXCEL (29 lines) From: Dexter Road <dexter_road@YAHOO.COM> Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Length of macro variablesLength of macro variables (14 lines) From: Pieter.Kirsten@CRONKITE.CC.UGA.EDU Re: Length of macro variables (24 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Length of macro variables (41 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Re: Length of macro variables (31 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
ListsLists (28 lines) From: Peter Flom <peter.flom@NDRI.ORG> Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Looking for a paper on generating random number in SASLooking for a paper on generating random number in SAS (45 lines) From: paula D <sophe@USA.NET> MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
MANOVAMANOVA (57 lines) From: Pedro G髆ez <pgt@EFBBVA.COM> Re: MANOVA (21 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: MANOVA (59 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
MS Outlook always warn about SAS send email?Re: MS Outlook always warn about SAS send email? (176 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Macro Code for ListingMacro Code for Listing (57 lines) From: A. L. <franz_cl2003@YAHOO.FR> Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Missing freqRe: Missing freq (29 lines) From: Paul Choate <pchoate@JPS.NET> Missing freq (15 lines) From: Simon Griffin <griffin_simon@HOTMAIL.COM> NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
NAV detected a virus in a document you authoredNAV detected a virus in a document you authored (17 lines) From: Il-ChicHub/Navigant@NAVIGANTCONSULTING.COM Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Nested Whitlock Do Loops?Re: Nested Whitlock Do Loops? (19 lines) From: Jens Schlatter <OAFGFZWETIVH@SPAMMOTEL.COM> Re: Nested Whitlock Do Loops? (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Nested Whitlock Do Loops? (52 lines) From: Perry Watts <wattsp@DCA.NET> Re: Nested Whitlock Do Loops? (145 lines) From: Paul Dorfman <paul_dorfman@HOTMAIL.COM> Re: Nested Whitlock Do Loops? (14 lines) From: Jens <jms0@GMX.DE> Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Next book?Next book? (17 lines) From: Steve <GUITARZEALOT@YAHOO.COM> Re: Next book? (21 lines) From: Paul Choate <pchoate@JPS.NET> Re: Next book? (35 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Next book? (50 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Next book? (21 lines) From: Ace <b.rogers@VIRGIN.NET> OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
OFFRE RESERVEE de d閏embre 2001OFFRE RESERVEE de d閏embre 2001 (1611 lines) From: emailing@PARTNERS-STORE.COM OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
OT: MS Outlook always warn about SAS send email?OT: MS Outlook always warn about SAS send email? (44 lines) From: Yu, Michael <michael.yu@SPCORP.COM> Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Observations generating random number paperObservations generating random number paper (19 lines) From: paula D <sophe@USA.NET> Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Only two decimal in summary statisticsRe: Only two decimal in summary statistics (25 lines) From: Vadim Pliner <vadim.pliner@VERIZONWIRELESS.COM> Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Oracle column and table commentsOracle column and table comments (41 lines) From: Gunnar Petersson <gunnar.petersson@MEP.KI.SE> Re: Oracle column and table comments (41 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
P value for Kolmogorov-SmirnovP value for Kolmogorov-Smirnov (15 lines) From: shiling zhang <shiling99@YAHOO.COM> Re: P value for Kolmogorov-Smirnov (28 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Pieldeleopardo reempalza Pluma y FuentePieldeleopardo reempalza Pluma y Fuente (88 lines) From: Pluma y Fuente <plumayfuente@PIELDELEOPARDO.COM> Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Printing BarcodesPrinting Barcodes (23 lines) From: Jim Manganello <Jim.Manganello@US.BOSCH.COM> Re: Printing Barcodes (45 lines) From: lpogoda <lpogoda@HOTMAIL.SPAMFREE.COM> Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Problem on Client-server signon, please helpProblem on Client-server signon, please help (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Problem on signon, please help!Problem on signon, please help! (16 lines) From: jonny <hzhuhoo@NETEASE.COM> Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Proc GLM on a poor designProc GLM on a poor design (32 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (48 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Proc GLM on a poor design (71 lines) From: Luo, Peter <pluo@DRAFTNET.COM> Re: Proc GLM on a poor design (88 lines) From: Anthony Kilili <Anthony.Kilili@BMGDIRECT.COM> Re: Proc GLM on a poor design (34 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Proc NETFLOW questions
Proc NETFLOW questions