(MVS): Re:Update statement/table indexes?(MVS): Re:Update statement/table indexes? (104 lines) From: RAITHEM <RAITHEM@WESTAT.COM> 4th Quarter KCASUG meetingRe: 4th Quarter KCASUG meeting (46 lines) From: steve.beakley@LABONE.COM @ Last weeks of December 99 - For Those Who Take Life Too Seriously@ Last weeks of December 99 - For Those Who Take Life Too Seriously (138 lines) From: gspatel@PEPCO.COM Re: @ Last weeks of December 99 - For Those Who Take Life Too Seriously (19 lines) From: Jaclyn Whitehorn <jaclyn@BAMA.UA.EDU> A > Q: informat w.d, decimal partA > Q: informat w.d, decimal part (62 lines) From: Peter Crawford <peter.crawford@DB.COM> A > Q: informat w.d, decimal part (Thanks!!)Re: A > Q: informat w.d, decimal part (Thanks!!) (36 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> A SAS ProblemA SAS Problem (76 lines) From: Wang, Zhaoping (PCM - NJ) <ZWang@NA2.US.ML.COM> Re: A SAS Problem (95 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: A SAS Problem (144 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Accessing DB2 UDB V5.1 for OS/390Accessing DB2 UDB V5.1 for OS/390 (76 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Accessing DB2 UDB V5.1 for OS/390 (53 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Achieved Probability ExplanationAchieved Probability Explanation (37 lines) From: Alan Neustadtl <aneustadtl@SOCY.UMD.EDU> Re: Achieved Probability Explanation (92 lines) From: Mark S Dehaan/MSD/LMITCO/INEEL/US <MSD@INEL.GOV> Antwort: Re: Need to detect empty file; How?Antwort: Re: Need to detect empty file; How? (42 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: Antwort: Re: Need to detect empty file; How? (67 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Antwort: Re: Problem: SAS LOG-window fullAntwort: Re: Problem: SAS LOG-window full (30 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Antwort: SV: Graphing in SASAntwort: SV: Graphing in SAS (23 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Any SAS Macro Tutorials out thereAny SAS Macro Tutorials out there (19 lines) From: Macro Man <macroman_1@HOTMAIL.COM> Re: Any SAS Macro Tutorials out there (35 lines) From: William W. Viergever <wwvierg@IBM.NET> Biostatisticians role in clinical trialsRe: Biostatisticians role in clinical trials (50 lines) From: machellew@MY-DEJA.COM Re: Biostatisticians role in clinical trials (39 lines) From: Rodney Sparapani <rodney.sparapani@DUKE.EDU> Re: Biostatisticians role in clinical trials (46 lines) From: Scott Moseley <moseley@VPHARM.COM> Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
4th Quarter KCASUG meetingRe: 4th Quarter KCASUG meeting (46 lines) From: steve.beakley@LABONE.COM @ Last weeks of December 99 - For Those Who Take Life Too Seriously@ Last weeks of December 99 - For Those Who Take Life Too Seriously (138 lines) From: gspatel@PEPCO.COM Re: @ Last weeks of December 99 - For Those Who Take Life Too Seriously (19 lines) From: Jaclyn Whitehorn <jaclyn@BAMA.UA.EDU> A > Q: informat w.d, decimal partA > Q: informat w.d, decimal part (62 lines) From: Peter Crawford <peter.crawford@DB.COM> A > Q: informat w.d, decimal part (Thanks!!)Re: A > Q: informat w.d, decimal part (Thanks!!) (36 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> A SAS ProblemA SAS Problem (76 lines) From: Wang, Zhaoping (PCM - NJ) <ZWang@NA2.US.ML.COM> Re: A SAS Problem (95 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: A SAS Problem (144 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Accessing DB2 UDB V5.1 for OS/390Accessing DB2 UDB V5.1 for OS/390 (76 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Accessing DB2 UDB V5.1 for OS/390 (53 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Achieved Probability ExplanationAchieved Probability Explanation (37 lines) From: Alan Neustadtl <aneustadtl@SOCY.UMD.EDU> Re: Achieved Probability Explanation (92 lines) From: Mark S Dehaan/MSD/LMITCO/INEEL/US <MSD@INEL.GOV> Antwort: Re: Need to detect empty file; How?Antwort: Re: Need to detect empty file; How? (42 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: Antwort: Re: Need to detect empty file; How? (67 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Antwort: Re: Problem: SAS LOG-window fullAntwort: Re: Problem: SAS LOG-window full (30 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Antwort: SV: Graphing in SASAntwort: SV: Graphing in SAS (23 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Any SAS Macro Tutorials out thereAny SAS Macro Tutorials out there (19 lines) From: Macro Man <macroman_1@HOTMAIL.COM> Re: Any SAS Macro Tutorials out there (35 lines) From: William W. Viergever <wwvierg@IBM.NET> Biostatisticians role in clinical trialsRe: Biostatisticians role in clinical trials (50 lines) From: machellew@MY-DEJA.COM Re: Biostatisticians role in clinical trials (39 lines) From: Rodney Sparapani <rodney.sparapani@DUKE.EDU> Re: Biostatisticians role in clinical trials (46 lines) From: Scott Moseley <moseley@VPHARM.COM> Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
@ Last weeks of December 99 - For Those Who Take Life Too Seriously@ Last weeks of December 99 - For Those Who Take Life Too Seriously (138 lines) From: gspatel@PEPCO.COM Re: @ Last weeks of December 99 - For Those Who Take Life Too Seriously (19 lines) From: Jaclyn Whitehorn <jaclyn@BAMA.UA.EDU> A > Q: informat w.d, decimal partA > Q: informat w.d, decimal part (62 lines) From: Peter Crawford <peter.crawford@DB.COM> A > Q: informat w.d, decimal part (Thanks!!)Re: A > Q: informat w.d, decimal part (Thanks!!) (36 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> A SAS ProblemA SAS Problem (76 lines) From: Wang, Zhaoping (PCM - NJ) <ZWang@NA2.US.ML.COM> Re: A SAS Problem (95 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: A SAS Problem (144 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Accessing DB2 UDB V5.1 for OS/390Accessing DB2 UDB V5.1 for OS/390 (76 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Accessing DB2 UDB V5.1 for OS/390 (53 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Achieved Probability ExplanationAchieved Probability Explanation (37 lines) From: Alan Neustadtl <aneustadtl@SOCY.UMD.EDU> Re: Achieved Probability Explanation (92 lines) From: Mark S Dehaan/MSD/LMITCO/INEEL/US <MSD@INEL.GOV> Antwort: Re: Need to detect empty file; How?Antwort: Re: Need to detect empty file; How? (42 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: Antwort: Re: Need to detect empty file; How? (67 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Antwort: Re: Problem: SAS LOG-window fullAntwort: Re: Problem: SAS LOG-window full (30 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Antwort: SV: Graphing in SASAntwort: SV: Graphing in SAS (23 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Any SAS Macro Tutorials out thereAny SAS Macro Tutorials out there (19 lines) From: Macro Man <macroman_1@HOTMAIL.COM> Re: Any SAS Macro Tutorials out there (35 lines) From: William W. Viergever <wwvierg@IBM.NET> Biostatisticians role in clinical trialsRe: Biostatisticians role in clinical trials (50 lines) From: machellew@MY-DEJA.COM Re: Biostatisticians role in clinical trials (39 lines) From: Rodney Sparapani <rodney.sparapani@DUKE.EDU> Re: Biostatisticians role in clinical trials (46 lines) From: Scott Moseley <moseley@VPHARM.COM> Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
A > Q: informat w.d, decimal partA > Q: informat w.d, decimal part (62 lines) From: Peter Crawford <peter.crawford@DB.COM> A > Q: informat w.d, decimal part (Thanks!!)Re: A > Q: informat w.d, decimal part (Thanks!!) (36 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> A SAS ProblemA SAS Problem (76 lines) From: Wang, Zhaoping (PCM - NJ) <ZWang@NA2.US.ML.COM> Re: A SAS Problem (95 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: A SAS Problem (144 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Accessing DB2 UDB V5.1 for OS/390Accessing DB2 UDB V5.1 for OS/390 (76 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Accessing DB2 UDB V5.1 for OS/390 (53 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Achieved Probability ExplanationAchieved Probability Explanation (37 lines) From: Alan Neustadtl <aneustadtl@SOCY.UMD.EDU> Re: Achieved Probability Explanation (92 lines) From: Mark S Dehaan/MSD/LMITCO/INEEL/US <MSD@INEL.GOV> Antwort: Re: Need to detect empty file; How?Antwort: Re: Need to detect empty file; How? (42 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: Antwort: Re: Need to detect empty file; How? (67 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Antwort: Re: Problem: SAS LOG-window fullAntwort: Re: Problem: SAS LOG-window full (30 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Antwort: SV: Graphing in SASAntwort: SV: Graphing in SAS (23 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Any SAS Macro Tutorials out thereAny SAS Macro Tutorials out there (19 lines) From: Macro Man <macroman_1@HOTMAIL.COM> Re: Any SAS Macro Tutorials out there (35 lines) From: William W. Viergever <wwvierg@IBM.NET> Biostatisticians role in clinical trialsRe: Biostatisticians role in clinical trials (50 lines) From: machellew@MY-DEJA.COM Re: Biostatisticians role in clinical trials (39 lines) From: Rodney Sparapani <rodney.sparapani@DUKE.EDU> Re: Biostatisticians role in clinical trials (46 lines) From: Scott Moseley <moseley@VPHARM.COM> Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
A > Q: informat w.d, decimal part (Thanks!!)Re: A > Q: informat w.d, decimal part (Thanks!!) (36 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> A SAS ProblemA SAS Problem (76 lines) From: Wang, Zhaoping (PCM - NJ) <ZWang@NA2.US.ML.COM> Re: A SAS Problem (95 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: A SAS Problem (144 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Accessing DB2 UDB V5.1 for OS/390Accessing DB2 UDB V5.1 for OS/390 (76 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Accessing DB2 UDB V5.1 for OS/390 (53 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Achieved Probability ExplanationAchieved Probability Explanation (37 lines) From: Alan Neustadtl <aneustadtl@SOCY.UMD.EDU> Re: Achieved Probability Explanation (92 lines) From: Mark S Dehaan/MSD/LMITCO/INEEL/US <MSD@INEL.GOV> Antwort: Re: Need to detect empty file; How?Antwort: Re: Need to detect empty file; How? (42 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: Antwort: Re: Need to detect empty file; How? (67 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Antwort: Re: Problem: SAS LOG-window fullAntwort: Re: Problem: SAS LOG-window full (30 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Antwort: SV: Graphing in SASAntwort: SV: Graphing in SAS (23 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Any SAS Macro Tutorials out thereAny SAS Macro Tutorials out there (19 lines) From: Macro Man <macroman_1@HOTMAIL.COM> Re: Any SAS Macro Tutorials out there (35 lines) From: William W. Viergever <wwvierg@IBM.NET> Biostatisticians role in clinical trialsRe: Biostatisticians role in clinical trials (50 lines) From: machellew@MY-DEJA.COM Re: Biostatisticians role in clinical trials (39 lines) From: Rodney Sparapani <rodney.sparapani@DUKE.EDU> Re: Biostatisticians role in clinical trials (46 lines) From: Scott Moseley <moseley@VPHARM.COM> Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
A SAS ProblemA SAS Problem (76 lines) From: Wang, Zhaoping (PCM - NJ) <ZWang@NA2.US.ML.COM> Re: A SAS Problem (95 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: A SAS Problem (144 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Accessing DB2 UDB V5.1 for OS/390Accessing DB2 UDB V5.1 for OS/390 (76 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Accessing DB2 UDB V5.1 for OS/390 (53 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Achieved Probability ExplanationAchieved Probability Explanation (37 lines) From: Alan Neustadtl <aneustadtl@SOCY.UMD.EDU> Re: Achieved Probability Explanation (92 lines) From: Mark S Dehaan/MSD/LMITCO/INEEL/US <MSD@INEL.GOV> Antwort: Re: Need to detect empty file; How?Antwort: Re: Need to detect empty file; How? (42 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: Antwort: Re: Need to detect empty file; How? (67 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Antwort: Re: Problem: SAS LOG-window fullAntwort: Re: Problem: SAS LOG-window full (30 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Antwort: SV: Graphing in SASAntwort: SV: Graphing in SAS (23 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Any SAS Macro Tutorials out thereAny SAS Macro Tutorials out there (19 lines) From: Macro Man <macroman_1@HOTMAIL.COM> Re: Any SAS Macro Tutorials out there (35 lines) From: William W. Viergever <wwvierg@IBM.NET> Biostatisticians role in clinical trialsRe: Biostatisticians role in clinical trials (50 lines) From: machellew@MY-DEJA.COM Re: Biostatisticians role in clinical trials (39 lines) From: Rodney Sparapani <rodney.sparapani@DUKE.EDU> Re: Biostatisticians role in clinical trials (46 lines) From: Scott Moseley <moseley@VPHARM.COM> Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Accessing DB2 UDB V5.1 for OS/390Accessing DB2 UDB V5.1 for OS/390 (76 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Accessing DB2 UDB V5.1 for OS/390 (53 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Achieved Probability ExplanationAchieved Probability Explanation (37 lines) From: Alan Neustadtl <aneustadtl@SOCY.UMD.EDU> Re: Achieved Probability Explanation (92 lines) From: Mark S Dehaan/MSD/LMITCO/INEEL/US <MSD@INEL.GOV> Antwort: Re: Need to detect empty file; How?Antwort: Re: Need to detect empty file; How? (42 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: Antwort: Re: Need to detect empty file; How? (67 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Antwort: Re: Problem: SAS LOG-window fullAntwort: Re: Problem: SAS LOG-window full (30 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Antwort: SV: Graphing in SASAntwort: SV: Graphing in SAS (23 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Any SAS Macro Tutorials out thereAny SAS Macro Tutorials out there (19 lines) From: Macro Man <macroman_1@HOTMAIL.COM> Re: Any SAS Macro Tutorials out there (35 lines) From: William W. Viergever <wwvierg@IBM.NET> Biostatisticians role in clinical trialsRe: Biostatisticians role in clinical trials (50 lines) From: machellew@MY-DEJA.COM Re: Biostatisticians role in clinical trials (39 lines) From: Rodney Sparapani <rodney.sparapani@DUKE.EDU> Re: Biostatisticians role in clinical trials (46 lines) From: Scott Moseley <moseley@VPHARM.COM> Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Achieved Probability ExplanationAchieved Probability Explanation (37 lines) From: Alan Neustadtl <aneustadtl@SOCY.UMD.EDU> Re: Achieved Probability Explanation (92 lines) From: Mark S Dehaan/MSD/LMITCO/INEEL/US <MSD@INEL.GOV> Antwort: Re: Need to detect empty file; How?Antwort: Re: Need to detect empty file; How? (42 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: Antwort: Re: Need to detect empty file; How? (67 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Antwort: Re: Problem: SAS LOG-window fullAntwort: Re: Problem: SAS LOG-window full (30 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Antwort: SV: Graphing in SASAntwort: SV: Graphing in SAS (23 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Any SAS Macro Tutorials out thereAny SAS Macro Tutorials out there (19 lines) From: Macro Man <macroman_1@HOTMAIL.COM> Re: Any SAS Macro Tutorials out there (35 lines) From: William W. Viergever <wwvierg@IBM.NET> Biostatisticians role in clinical trialsRe: Biostatisticians role in clinical trials (50 lines) From: machellew@MY-DEJA.COM Re: Biostatisticians role in clinical trials (39 lines) From: Rodney Sparapani <rodney.sparapani@DUKE.EDU> Re: Biostatisticians role in clinical trials (46 lines) From: Scott Moseley <moseley@VPHARM.COM> Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Antwort: Re: Need to detect empty file; How?Antwort: Re: Need to detect empty file; How? (42 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: Antwort: Re: Need to detect empty file; How? (67 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Antwort: Re: Problem: SAS LOG-window fullAntwort: Re: Problem: SAS LOG-window full (30 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Antwort: SV: Graphing in SASAntwort: SV: Graphing in SAS (23 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Any SAS Macro Tutorials out thereAny SAS Macro Tutorials out there (19 lines) From: Macro Man <macroman_1@HOTMAIL.COM> Re: Any SAS Macro Tutorials out there (35 lines) From: William W. Viergever <wwvierg@IBM.NET> Biostatisticians role in clinical trialsRe: Biostatisticians role in clinical trials (50 lines) From: machellew@MY-DEJA.COM Re: Biostatisticians role in clinical trials (39 lines) From: Rodney Sparapani <rodney.sparapani@DUKE.EDU> Re: Biostatisticians role in clinical trials (46 lines) From: Scott Moseley <moseley@VPHARM.COM> Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Antwort: Re: Problem: SAS LOG-window fullAntwort: Re: Problem: SAS LOG-window full (30 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Antwort: SV: Graphing in SASAntwort: SV: Graphing in SAS (23 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Any SAS Macro Tutorials out thereAny SAS Macro Tutorials out there (19 lines) From: Macro Man <macroman_1@HOTMAIL.COM> Re: Any SAS Macro Tutorials out there (35 lines) From: William W. Viergever <wwvierg@IBM.NET> Biostatisticians role in clinical trialsRe: Biostatisticians role in clinical trials (50 lines) From: machellew@MY-DEJA.COM Re: Biostatisticians role in clinical trials (39 lines) From: Rodney Sparapani <rodney.sparapani@DUKE.EDU> Re: Biostatisticians role in clinical trials (46 lines) From: Scott Moseley <moseley@VPHARM.COM> Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Antwort: SV: Graphing in SASAntwort: SV: Graphing in SAS (23 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Any SAS Macro Tutorials out thereAny SAS Macro Tutorials out there (19 lines) From: Macro Man <macroman_1@HOTMAIL.COM> Re: Any SAS Macro Tutorials out there (35 lines) From: William W. Viergever <wwvierg@IBM.NET> Biostatisticians role in clinical trialsRe: Biostatisticians role in clinical trials (50 lines) From: machellew@MY-DEJA.COM Re: Biostatisticians role in clinical trials (39 lines) From: Rodney Sparapani <rodney.sparapani@DUKE.EDU> Re: Biostatisticians role in clinical trials (46 lines) From: Scott Moseley <moseley@VPHARM.COM> Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Any SAS Macro Tutorials out thereAny SAS Macro Tutorials out there (19 lines) From: Macro Man <macroman_1@HOTMAIL.COM> Re: Any SAS Macro Tutorials out there (35 lines) From: William W. Viergever <wwvierg@IBM.NET> Biostatisticians role in clinical trialsRe: Biostatisticians role in clinical trials (50 lines) From: machellew@MY-DEJA.COM Re: Biostatisticians role in clinical trials (39 lines) From: Rodney Sparapani <rodney.sparapani@DUKE.EDU> Re: Biostatisticians role in clinical trials (46 lines) From: Scott Moseley <moseley@VPHARM.COM> Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Biostatisticians role in clinical trialsRe: Biostatisticians role in clinical trials (50 lines) From: machellew@MY-DEJA.COM Re: Biostatisticians role in clinical trials (39 lines) From: Rodney Sparapani <rodney.sparapani@DUKE.EDU> Re: Biostatisticians role in clinical trials (46 lines) From: Scott Moseley <moseley@VPHARM.COM> Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Boston Job OppsBoston Job Opps (12 lines) From: Mike Murphy <mmurphy@WORLD.STD.COM> Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Coder's ContestCoder's Contest (29 lines) From: Berryhill, Tim <TWB2@PGE.COM> Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Compare Two RecordsCompare Two Records (25 lines) From: Dan Keating <keatingd@WASHPOST.COM> Re: Compare Two Records (48 lines) From: RHOADSM1 <RHOADSM1@WESTAT.COM> Re: Compare Two Records (41 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: Compare Two Records (43 lines) From: HERMANS1 <HERMANS1@WESTAT.COM> Re: Compare Two Records (143 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Creating MVS PDS with SASRe: Creating MVS PDS with SAS (49 lines) From: Herman Jacobs <herman.jacobs@CMG.BE> Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Customized FSEDIT, problems setting an edit flagCustomized FSEDIT, problems setting an edit flag (39 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Re: Customized FSEDIT, problems setting an edit flag (57 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: Customized FSEDIT, problems setting an edit flag (9 lines) From: Robin baker <rdbaker@SYMPATICO.CA> Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Datawarehouses Powermart - SASDatawarehouses Powermart - SAS (41 lines) From: Gerold Nicolasen <gerold.nicolasen@EOMDATA.NL> Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Deceptive problem with 'retain'Deceptive problem with 'retain' (42 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Re: Deceptive problem with 'retain' (74 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: Deceptive problem with 'retain' (32 lines) From: Kyle Dane <kyledane@MY-DEJA.COM> Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Degree of freedom - proc mixedRe: Degree of freedom - proc mixed (34 lines) From: Jesse Chittams <jesse@LANDRU.CPR.UPENN.EDU> Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Distance betwen ZIP codesDistance betwen ZIP codes (34 lines) From: Blodgett, John G. <BlodgettJ@UMSYSTEM.EDU> Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Elephants ... was: RE: Help RequiredElephants ... was: RE: Help Required (57 lines) From: William W. Viergever <wwvierg@IBM.NET> Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Error Code YZBMLOK0Error Code YZBMLOK0 (37 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Re: Error Code YZBMLOK0 (85 lines) From: Dennis Diskin <Dennis.Diskin.B@BAYER.COM> Re: Error Code YZBMLOK0 (94 lines) From: Burgess Evans <BMEVANS@AUDITOR.STATE.OH.US> Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Excel 5.0 (Office 4.3) failureExcel 5.0 (Office 4.3) failure (31 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> Re: Excel 5.0 (Office 4.3) failure (36 lines) From: Kevin F. Spratt <Kevin-Spratt@UIOWA.EDU> FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
FTP Frpm Unix to Novell ServersFTP Frpm Unix to Novell Servers (12 lines) From: Steven K Silver <steve.silver@CRESTAR.COM> FTP Frpm Unix to Novell Servers (17 lines) From: silver0514@MY-DEJA.COM FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
FW: Antwort: Re: Problem: SAS LOG-window fullFW: Antwort: Re: Problem: SAS LOG-window full (40 lines) From: Meshkovsky, Paul <PMeshkovsky@FLEETCC.COM> FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
FW: Ordering variables in data stepFW: Ordering variables in data step (30 lines) From: Shostak, Jack <shost001@ONYX.DCRI.DUKE.EDU> Re: FW: Ordering variables in data step (48 lines) From: silver0514@MY-DEJA.COM FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
FormChar for Pretty Boxes on HP4M Plus PrinterFormChar for Pretty Boxes on HP4M Plus Printer (16 lines) From: IDataSolns <idatasolns@AOL.COM> Re: FormChar for Pretty Boxes on HP4M Plus Printer (34 lines) From: William W. Viergever <wwvierg@IBM.NET> Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Format name length restrictionFormat name length restriction (18 lines) From: Nigel Tufnel <dousk8@HOTMAIL.COM> Re: Format name length restriction (34 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Format name length restriction (63 lines) From: Richard Read Allen <rrallen@IBM.NET> Re: Format name length restriction (66 lines) From: Jack Shoemaker <JShoemaker@ACCORDANT.NET> Re: Format name length restriction (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Format name length restriction (62 lines) From: Peter Crawford <peter.crawford@DB.COM> Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Free alternatives to Base/SASRe: Free alternatives to Base/SAS (37 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (29 lines) From: Jeremy Gurney <c4jgurney@MY-DEJA.COM> Re: Free alternatives to Base/SAS (33 lines) From: Earl Westerlund <earl.westerlund@KODAK.COM> Re: Free alternatives to Base/SAS (28 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (65 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (97 lines) From: Walt Smith <walter_smith@MY-DEJA.COM> Re: Free alternatives to Base/SAS (124 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Free alternatives to Base/SAS (170 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (51 lines) From: Tim Churches <tchur@BIGPOND.COM> Re: Free alternatives to Base/SAS (85 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Re: Free alternatives to Base/SAS (69 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Free alternatives to Base/SAS (28 lines) From: Andrea Wainwright <andrea.wainwright@CAPITALONE.COM> GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
GLM DifferencesGLM Differences (62 lines) From: Warren Schlechte <wschlech@KTC.COM> Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Giving a valueGiving a value (45 lines) From: Pierre Dostie <pdostie@GROUPAMA-CCAMA.TM.FR> Re: Giving a value (74 lines) From: WIELKI Andre <wielki@INED.FR> Re: Giving a value (81 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Graphing in SASGraphing in SAS (18 lines) From: Iain Babeu <ibabeu@NOSPAM.CADMUSGROUP.COM> Re: Graphing in SAS (24 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Graphing in SAS (32 lines) From: Mark Brigham <mbrigham@USGS.GOV> Re: Graphing in SAS (141 lines) From: James Carvalho <jjc@ASU.EDU> Re: Graphing in SAS (49 lines) From: Paul OldenKamp <paul.oldenkamp@BOEING.COM> Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Graphing in SAS (boxplots)Re: Graphing in SAS (boxplots) (31 lines) From: Michael Friendly <friendly@HOTSPUR.PSYCH.YORKU.CA> Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Hardware Requirements for Best SAS PerformanceHardware Requirements for Best SAS Performance (28 lines) From: charles_patridge@MY-DEJA.COM Hardware Requirements for Best SAS Performance (31 lines) From: charles_patridge@MY-DEJA.COM Re: Hardware Requirements for Best SAS Performance (50 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Help RequiredHelp Required (29 lines) From: Selvaraj, SureshKumar (IMS Plymouth) <SKSelvaraj@US.IMSHEALTH.COM> Re: Help Required (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Help Required (63 lines) From: Michael.Thomas@EQUIFAX.COM Re: Help Required (46 lines) From: Mary Whelan <g9220mwhel@UMBSKY.CC.UMB.EDU> Re: Help Required (78 lines) From: William W. Viergever <wwvierg@IBM.NET> Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Help loading a IML Module from an External ASCII file.Help loading a IML Module from an External ASCII file. (20 lines) From: Steven R. Miller <millesr@OKSTATE.EDU> Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Help with MAPSHelp with MAPS (23 lines) From: E. Shields <shields@MED.MCGILL.CA> Re: Help with MAPS (90 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (71 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: Help with MAPS (32 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Help: distance between zip codesHelp: distance between zip codes (17 lines) From: Kent Andrew (Drew) Spencer <drewspen@IMAGIN.NET> Re: Help: distance between zip codes (13 lines) From: CHUCK MAKINSON <clmakinson@GOODYEAR.COM> Re: Help: distance between zip codes (17 lines) From: SAlbert <salbert@AOL.COMSTOPSPAM> Re: Help: distance between zip codes (27 lines) From: dward <dwardNOdwSPAM@SASHELP.COM.INVALID> Re: Help: distance between zip codes (43 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Help: distance between zip codes (38 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Help: distance between zip codes (59 lines) From: charles_patridge@MY-DEJA.COM Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Homogeneity of CorrelationsHomogeneity of Correlations (16 lines) From: Jill Hough <jhough@OKSTATE.EDU> How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
How to get the likelihoods of each observation when doing FIMLHow to get the likelihoods of each observation when doing FIML (54 lines) From: Sudhir Karunakaran <ksudhir@STERN.NYU.EDU> How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
How to include missing values on UpdateHow to include missing values on Update (16 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: How to include missing values on Update (19 lines) From: Keith Branton <kdb@GLOBALNET.CO.UK> Re: How to include missing values on Update (44 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: How to include missing values on Update (96 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
How to modify Format/informatHow to modify Format/informat (33 lines) From: Panos PAPANIKOLAOU <PapanikolaouP@CARDIFF.AC.UK> Re: How to modify Format/informat (60 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: How to modify Format/informat (64 lines) From: Berryhill, Tim <TWB2@PGE.COM> Re: How to modify Format/informat (102 lines) From: Anthony.Kilili@BMGDIRECT.COM How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
How to summarize proc summary output?How to summarize proc summary output? (52 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (68 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: How to summarize proc summary output? (75 lines) From: Kick SAS <anonymous@COTSE.COM> Re: How to summarize proc summary output? (131 lines) From: Ian S Black <ian_s_black@STANDARDLIFE.COM> Re: How to summarize proc summary output? (139 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Re: How to summarize proc summary output? (48 lines) From: amichiel@EARTHLING.NET Re: How to summarize proc summary output? (92 lines) From: Peter Crawford <peter.crawford@DB.COM> How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
How to unsubscribeHow to unsubscribe (14 lines) From: Ming Hsu <athxu@HONORS.ARIZONA.EDU> How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
How to unsubscribe,thanksHow to unsubscribe,thanks (14 lines) From: elmaache hamani <elmaache@HOTMAIL.COM> IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
IS a GUI possible with SAS? (Visual C++)IS a GUI possible with SAS? (Visual C++) (32 lines) From: Shalin <shalinsh@ALUDRA.USC.EDU> Re: IS a GUI possible with SAS? (Visual C++) (47 lines) From: Jules Bosch <bsi@NAC.NET> Re: IS a GUI possible with SAS? (Visual C++) (32 lines) From: Weimin Hua <Wmhua@AOL.COM> Re: IS a GUI possible with SAS? (Visual C++) (86 lines) From: Bernard Tremblay <bernard@CAPITALE.QC.CA> Re: IS a GUI possible with SAS? (Visual C++) (21 lines) From: Shalin <shalinsh@USC.EDU> Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Inexpensive alternatives to Base/SASInexpensive alternatives to Base/SAS (19 lines) From: George Anderson <george_anderson_carter@YAHOO.COM> Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Info about CompuStatRe: Info about CompuStat (43 lines) From: Kevin Brunson <kbrunson@ND.EDU> Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Job opening - pharmaceutical - Philadelphia areaJob opening - pharmaceutical - Philadelphia area (43 lines) From: Dirk Spruck <SPRUCD@CENTEON.COM> Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Lag function and by groupsLag function and by groups (20 lines) From: Henry Feldman <hfeldman@CONCEPTUAL.COM> Lag function and by groups (51 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Lag function and by groups (62 lines) From: Howard Schreier <Howard_Schreier@ITA.DOC.GOV> Re: Lag function and by groups (34 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Lag function and by groups (34 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
LinuxLinux (15 lines) From: Mail <cosh@DCA.NET> Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Macro Variables in RSUBMIT CodeMacro Variables in RSUBMIT Code (19 lines) From: Peter Hills <peter_hills@MY-DEJA.COM> Macro Variables in RSUBMIT Code (40 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Macro Variables in RSUBMIT Code (32 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (42 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Macro Variables in RSUBMIT Code (9 lines) From: armel.francois <armel.francois@WANADOO.FR> Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Macro questionRe: Macro question (46 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Macro question (64 lines) From: Peter Crawford <peter.crawford@DB.COM> Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Multi-States modelsMulti-States models (28 lines) From: MOUVEROUX Vincent <Vincent.MOUVEROUX@GEP.FR> Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Need advice on bootstrapping/CV/jackknifingNeed advice on bootstrapping/CV/jackknifing (69 lines) From: Brad <macroman_1@HOTMAIL.COM> Re: Need advice on bootstrapping/CV/jackknifing (41 lines) From: Andrew Ratcliffe <aratcliffe@CIX.COMPULINK.CO.UK> Re: Need advice on bootstrapping/CV/jackknifing (34 lines) From: Paige Miller <paige.miller@KODAK.COM> Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Need help on PROC FACTORNeed help on PROC FACTOR (14 lines) From: Diana Šimić <dsimic@IMI.HR> Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Need to detect empty file; How?Re: Need to detect empty file; How? (102 lines) From: Paul M. Dorfman <sashole@EARTHLINK.NET> Re: Need to detect empty file; How? (51 lines) From: The GIANT chinese <yungyang.hu@NIKLASDATA.NL> Re: Need to detect empty file; How? (54 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Need to detect empty file; How? (94 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Need to detect empty file; How? (56 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Not quite zero valuesNot quite zero values (63 lines) From: Joel Winter <jpwinter@UMSL.EDU> Re: Not quite zero values (22 lines) From: dkb@CIX.COMPULINK.CO.UK Re: Not quite zero values (82 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: Not quite zero values (27 lines) From: Thibaud Taudin Chabot <tchabot@KLM.NL> Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS.Oprah, Nightline, Maria Shriver, 48 Hours, 20/20 and more have all interviewed this famous Private Investigator. Now, you too, can make a substantial income using Schweitzers highly sought- after SECRETS. (112 lines) From: Al <lAstchance@CASH.COM> Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Oracles Dates, SAS Access & Pass-ThruOracles Dates, SAS Access & Pass-Thru (45 lines) From: amichiel@EARTHLING.NET Re: Oracles Dates, SAS Access & Pass-Thru (65 lines) From: silver0514@MY-DEJA.COM Re: Oracles Dates, SAS Access & Pass-Thru (86 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Ordering variables in data stepOrdering variables in data step (15 lines) From: EASTWOD <EASTWOD@WESTAT.COM> Re: Ordering variables in data step (25 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Re: Ordering variables in data step (31 lines) From: Asghar, Arthur <Arthur.Asghar@PHARMA.COM> Re: Ordering variables in data step (18 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> Re: Ordering variables in data step (75 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: Ordering variables in data step (22 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> RE(ason for): Ordering variables in data step (39 lines) From: Edel, Christoph (Frankfurt) <CEdel@DE.IMSHEALTH.COM> Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Orientation of graphics outputOrientation of graphics output (33 lines) From: Lund, Pete <Peter.Lund@CFC.WA.GOV> Re: Orientation of graphics output (14 lines) From: Walter Smith <wjsmith1NOwjSPAM@FEDEX.COM.INVALID> Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Outliers in PROC LOGISTIC and IMLOutliers in PROC LOGISTIC and IML (26 lines) From: Eric VonDohlen <hollydays@WORLDNET.ATT.NET> Re: Outliers in PROC LOGISTIC and IML (37 lines) From: Walter Davis <walter_davis@UNC.EDU> PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
PC Program SchedulerRe: PC Program Scheduler (35 lines) From: Dmitry Hindanov <hindanov@BLACK-HOLE.COM> PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
PROC TABULATE Help Needed!PROC TABULATE Help Needed! (34 lines) From: Ray Wilt <rawilt@ACAD.URSINUS.EDU> Re: PROC TABULATE Help Needed! (61 lines) From: Lauren E Haworth <haworthl@MINDSPRING.COM> Re: PROC TABULATE Help Needed! (15 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
PerlPerl (15 lines) From: Mail <cosh@DCA.NET> Re: Perl (29 lines) From: William W. Viergever <wwvierg@IBM.NET> Re: Perl (32 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Re: Perl (25 lines) From: TheZone News <ctuck@DANSYS.COM> Re: Perl (55 lines) From: Michael S Hines <mshines@PURDUE.EDU> Re: Perl (34 lines) From: David Cassell <cassell@MERCURY.COR.EPA.GOV> Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Perl/DBI/ODBC: Connect error-Invalid String or Buffer LengthPerl/DBI/ODBC: Connect error-Invalid String or Buffer Length (74 lines) From: jkort@WIMBERLEY-TX.COM Re: Perl/DBI/ODBC: Connect error-Invalid String or Buffer Length (91 lines) From: Tim CHURCHES <TCHUR@DOH.HEALTH.NSW.GOV.AU> Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Permanent, Fulltime SAS Job in So. CaliforniaPermanent, Fulltime SAS Job in So. California (51 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanent, Fulltime SAS Job in So. California (51 lines) From: Roland <roland.rashleigh-berry@VIRGIN.NET> Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Permanet, Fulltime SAS Job in So. Cal (response to Roland)Permanet, Fulltime SAS Job in So. Cal (response to Roland) (20 lines) From: Tracy_Cermack@AHM.HONDA.COM Re: Permanet, Fulltime SAS Job in So. Cal (response to Roland) (24 lines) From: Frank Schiffel <SchifF@MAIL.HEALTH.STATE.MO.US> PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
PolyAnalyst 4.0 - Final Release of the Leading Data Mining SolutionPolyAnalyst 4.0 - Final Release of the Leading Data Mining Solution (124 lines) From: Sergei Ananyan <s.ananyan@MEGAPUTER.COM> PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
PrecisionPrecision (34 lines) From: Neil Simpson <Neil.Simpson@NATWEST.COM> Re: Precision (51 lines) From: Celina Zetterstrom Wilf <czw@SPARKRON.DK> Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Print OverrunPrint Overrun (31 lines) From: Werner E. HELM <helm@FH-DARMSTADT.DE> Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Problem: SAS LOG-window fullRe: Problem: SAS LOG-window full (42 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Re: Problem: SAS LOG-window full (87 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Proc Logistic stats questionProc Logistic stats question (21 lines) From: Joanne Mor <jmor@HAWAII.EDU> Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Q: Survival analyses of bioassaysQ: Survival analyses of bioassays (29 lines) From: Daniel Stahl <daniel_stahl@WEB.DE> Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Q: input function and informat w.d, w. bestw.Q: input function and informat w.d, w. bestw. (38 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Q: retrieve PROC PRINTTO destinies of LOG and PRINTQ: retrieve PROC PRINTTO destinies of LOG and PRINT (53 lines) From: Jim Groeneveld <J.Groeneveld@ITGROUPS.COM> Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
Q: tricky data management problemQ: tricky data management problem (91 lines) From: Christian F.G. Schendera <cschende@IX.URZ.UNI-HEIDELBERG.DE> RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
RE(ason for): Ordering variables in data stepRe: RE(ason for): Ordering variables in data step (50 lines) From: John Iwaniszek <john_iwaniszek@WORLDNET.ATT.NET> Re: RE(ason for): Ordering variables in data step (113 lines) From: Gehard Hellriegel <detecsm_hellriegelg@WESTLB.DE> Re: RE(ason for): Ordering variables in data step (18 lines) From: Ya Huang <Y.Huang@ORGANONINC.COM> Re: RE(ason for): Ordering variables in data step (59 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: RE(ason for): Ordering variables in data step (18 lines) From: Schechter Robert RS <robert.schechter@ASTRAZENECA.COM> Re: RE(ason for): Ordering variables in data step (14 lines) From: Robert Virgile <virgile@MEDIAONE.NET> Re: RE(ason for): Ordering variables in data step (102 lines) From: Waters, Jeremy <WatersJeremy@PRAINTL.COM> Re: RE(ason for): Ordering variables in data step (39 lines) From: Lou Pogoda <lpogoda@HOME.NOSPAM.COM> Re: RE(ason for): Ordering variables in data step (30 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> RETAIN or NOT RETAIN ?
RETAIN or NOT RETAIN ?