$100 SCONSIG Logo Contest - Kris Bogaerts$100 SCONSIG Logo Contest - Kris Bogaerts (22 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> <No subject><No subject> (45 lines) From: Bolen, Marty <mbolen@BUS.OLEMISS.EDU> <No subject> (39 lines) From: kviel <kviel@GMCF.ORG> <No subject> (40 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> <No subject> (20 lines) From: Guzzino, Lawrence <LGuzzino@CTB.COM> <No subject> (31 lines) From: Kit Leung <hello_joecool@HOTMAIL.COM> <No subject> (94 lines) From: Philip Crane <Philip_Crane@WORKCOVER.VIC.GOV.AU> Antwort: RE: Easiest way to drop all-missing variablesAntwort: RE: Easiest way to drop all-missing variables (184 lines) From: Peter Crawford <peter.crawford@DB.COM> Antwort: RE: Easiest way to drop all-missing variables (194 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Antwort: RE: Easiest way to drop all-missing variables (214 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Antwort: Where IS Language Reference in v8.1?Antwort: Where IS Language Reference in v8.1? (70 lines) From: Peter Crawford <peter.crawford@DB.COM> Antwort: Writing to multiple Excel sheetsAntwort: Writing to multiple Excel sheets (86 lines) From: Peter Crawford <peter.crawford@DB.COM> Any way to embed the sas code inside the data setAny way to embed the sas code inside the data set (15 lines) From: pAyp <pauladx@HOME.COM> Re: Any way to embed the sas code inside the data set (38 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Any way to embed the sas code inside the data set (25 lines) From: Kevin Elliott <kevinelliott@HOTMAIL.COM> Re: Any way to embed the sas code inside the data set (27 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> Re: Any way to embed the sas code inside the data set (31 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Any way to embed the sas code inside the data set (30 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Any way to embed the sas code inside the data set (44 lines) From: pAyp <pauladx@HOME.COM> Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099)Re: Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099) (85 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Are you a foreign resident? 353834Are you a foreign resident? 353834 (61 lines) From: mike2343@btinternet.com <mike2343@BTINTERNET.COM> Audit toolsAudit tools (37 lines) From: Bernard Tremblay <imaginasys@HOTMAIL.COM> Re: Audit tools (49 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> CHAID ResourcesCHAID Resources (12 lines) From: Brooks, Simon - CSG <Simon.Brooks@HAYSCSG.COM> Re: CHAID Resources (29 lines) From: Well Howell <whowell@SUPERLINK.NET> Re: CHAID Resources (40 lines) From: Roger DeAngelis <xlr82sas@AOL.COM> Re: CHAID Resources (16 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Can range be controlled in a N(0,1) distribution?Can range be controlled in a N(0,1) distribution? (165 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (58 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Can range be controlled in a N(0,1) distribution? (64 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (40 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Change in Mixed languageChange in Mixed language (51 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (67 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (137 lines) From: Rodney Sparapani <rsparapa@MCW.EDU> Re: Change in Mixed language (22 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (23 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Combine two filesCombine two files (35 lines) From: Graeme Kirton <gkirton@FILCS.COM> Re: Combine two files (20 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Combine two files (81 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
<No subject><No subject> (45 lines) From: Bolen, Marty <mbolen@BUS.OLEMISS.EDU> <No subject> (39 lines) From: kviel <kviel@GMCF.ORG> <No subject> (40 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> <No subject> (20 lines) From: Guzzino, Lawrence <LGuzzino@CTB.COM> <No subject> (31 lines) From: Kit Leung <hello_joecool@HOTMAIL.COM> <No subject> (94 lines) From: Philip Crane <Philip_Crane@WORKCOVER.VIC.GOV.AU> Antwort: RE: Easiest way to drop all-missing variablesAntwort: RE: Easiest way to drop all-missing variables (184 lines) From: Peter Crawford <peter.crawford@DB.COM> Antwort: RE: Easiest way to drop all-missing variables (194 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Antwort: RE: Easiest way to drop all-missing variables (214 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Antwort: Where IS Language Reference in v8.1?Antwort: Where IS Language Reference in v8.1? (70 lines) From: Peter Crawford <peter.crawford@DB.COM> Antwort: Writing to multiple Excel sheetsAntwort: Writing to multiple Excel sheets (86 lines) From: Peter Crawford <peter.crawford@DB.COM> Any way to embed the sas code inside the data setAny way to embed the sas code inside the data set (15 lines) From: pAyp <pauladx@HOME.COM> Re: Any way to embed the sas code inside the data set (38 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Any way to embed the sas code inside the data set (25 lines) From: Kevin Elliott <kevinelliott@HOTMAIL.COM> Re: Any way to embed the sas code inside the data set (27 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> Re: Any way to embed the sas code inside the data set (31 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Any way to embed the sas code inside the data set (30 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Any way to embed the sas code inside the data set (44 lines) From: pAyp <pauladx@HOME.COM> Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099)Re: Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099) (85 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Are you a foreign resident? 353834Are you a foreign resident? 353834 (61 lines) From: mike2343@btinternet.com <mike2343@BTINTERNET.COM> Audit toolsAudit tools (37 lines) From: Bernard Tremblay <imaginasys@HOTMAIL.COM> Re: Audit tools (49 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> CHAID ResourcesCHAID Resources (12 lines) From: Brooks, Simon - CSG <Simon.Brooks@HAYSCSG.COM> Re: CHAID Resources (29 lines) From: Well Howell <whowell@SUPERLINK.NET> Re: CHAID Resources (40 lines) From: Roger DeAngelis <xlr82sas@AOL.COM> Re: CHAID Resources (16 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Can range be controlled in a N(0,1) distribution?Can range be controlled in a N(0,1) distribution? (165 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (58 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Can range be controlled in a N(0,1) distribution? (64 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (40 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Change in Mixed languageChange in Mixed language (51 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (67 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (137 lines) From: Rodney Sparapani <rsparapa@MCW.EDU> Re: Change in Mixed language (22 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (23 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Combine two filesCombine two files (35 lines) From: Graeme Kirton <gkirton@FILCS.COM> Re: Combine two files (20 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Combine two files (81 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Antwort: RE: Easiest way to drop all-missing variablesAntwort: RE: Easiest way to drop all-missing variables (184 lines) From: Peter Crawford <peter.crawford@DB.COM> Antwort: RE: Easiest way to drop all-missing variables (194 lines) From: Peter Crawford <peter.crawford@DB.COM> Re: Antwort: RE: Easiest way to drop all-missing variables (214 lines) From: Chakravarthy, Venky <Venky.Chakravarthy@PFIZER.COM> Antwort: Where IS Language Reference in v8.1?Antwort: Where IS Language Reference in v8.1? (70 lines) From: Peter Crawford <peter.crawford@DB.COM> Antwort: Writing to multiple Excel sheetsAntwort: Writing to multiple Excel sheets (86 lines) From: Peter Crawford <peter.crawford@DB.COM> Any way to embed the sas code inside the data setAny way to embed the sas code inside the data set (15 lines) From: pAyp <pauladx@HOME.COM> Re: Any way to embed the sas code inside the data set (38 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Any way to embed the sas code inside the data set (25 lines) From: Kevin Elliott <kevinelliott@HOTMAIL.COM> Re: Any way to embed the sas code inside the data set (27 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> Re: Any way to embed the sas code inside the data set (31 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Any way to embed the sas code inside the data set (30 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Any way to embed the sas code inside the data set (44 lines) From: pAyp <pauladx@HOME.COM> Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099)Re: Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099) (85 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Are you a foreign resident? 353834Are you a foreign resident? 353834 (61 lines) From: mike2343@btinternet.com <mike2343@BTINTERNET.COM> Audit toolsAudit tools (37 lines) From: Bernard Tremblay <imaginasys@HOTMAIL.COM> Re: Audit tools (49 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> CHAID ResourcesCHAID Resources (12 lines) From: Brooks, Simon - CSG <Simon.Brooks@HAYSCSG.COM> Re: CHAID Resources (29 lines) From: Well Howell <whowell@SUPERLINK.NET> Re: CHAID Resources (40 lines) From: Roger DeAngelis <xlr82sas@AOL.COM> Re: CHAID Resources (16 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Can range be controlled in a N(0,1) distribution?Can range be controlled in a N(0,1) distribution? (165 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (58 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Can range be controlled in a N(0,1) distribution? (64 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (40 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Change in Mixed languageChange in Mixed language (51 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (67 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (137 lines) From: Rodney Sparapani <rsparapa@MCW.EDU> Re: Change in Mixed language (22 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (23 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Combine two filesCombine two files (35 lines) From: Graeme Kirton <gkirton@FILCS.COM> Re: Combine two files (20 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Combine two files (81 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Antwort: Where IS Language Reference in v8.1?Antwort: Where IS Language Reference in v8.1? (70 lines) From: Peter Crawford <peter.crawford@DB.COM> Antwort: Writing to multiple Excel sheetsAntwort: Writing to multiple Excel sheets (86 lines) From: Peter Crawford <peter.crawford@DB.COM> Any way to embed the sas code inside the data setAny way to embed the sas code inside the data set (15 lines) From: pAyp <pauladx@HOME.COM> Re: Any way to embed the sas code inside the data set (38 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Any way to embed the sas code inside the data set (25 lines) From: Kevin Elliott <kevinelliott@HOTMAIL.COM> Re: Any way to embed the sas code inside the data set (27 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> Re: Any way to embed the sas code inside the data set (31 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Any way to embed the sas code inside the data set (30 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Any way to embed the sas code inside the data set (44 lines) From: pAyp <pauladx@HOME.COM> Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099)Re: Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099) (85 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Are you a foreign resident? 353834Are you a foreign resident? 353834 (61 lines) From: mike2343@btinternet.com <mike2343@BTINTERNET.COM> Audit toolsAudit tools (37 lines) From: Bernard Tremblay <imaginasys@HOTMAIL.COM> Re: Audit tools (49 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> CHAID ResourcesCHAID Resources (12 lines) From: Brooks, Simon - CSG <Simon.Brooks@HAYSCSG.COM> Re: CHAID Resources (29 lines) From: Well Howell <whowell@SUPERLINK.NET> Re: CHAID Resources (40 lines) From: Roger DeAngelis <xlr82sas@AOL.COM> Re: CHAID Resources (16 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Can range be controlled in a N(0,1) distribution?Can range be controlled in a N(0,1) distribution? (165 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (58 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Can range be controlled in a N(0,1) distribution? (64 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (40 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Change in Mixed languageChange in Mixed language (51 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (67 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (137 lines) From: Rodney Sparapani <rsparapa@MCW.EDU> Re: Change in Mixed language (22 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (23 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Combine two filesCombine two files (35 lines) From: Graeme Kirton <gkirton@FILCS.COM> Re: Combine two files (20 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Combine two files (81 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Antwort: Writing to multiple Excel sheetsAntwort: Writing to multiple Excel sheets (86 lines) From: Peter Crawford <peter.crawford@DB.COM> Any way to embed the sas code inside the data setAny way to embed the sas code inside the data set (15 lines) From: pAyp <pauladx@HOME.COM> Re: Any way to embed the sas code inside the data set (38 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Any way to embed the sas code inside the data set (25 lines) From: Kevin Elliott <kevinelliott@HOTMAIL.COM> Re: Any way to embed the sas code inside the data set (27 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> Re: Any way to embed the sas code inside the data set (31 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Any way to embed the sas code inside the data set (30 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Any way to embed the sas code inside the data set (44 lines) From: pAyp <pauladx@HOME.COM> Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099)Re: Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099) (85 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Are you a foreign resident? 353834Are you a foreign resident? 353834 (61 lines) From: mike2343@btinternet.com <mike2343@BTINTERNET.COM> Audit toolsAudit tools (37 lines) From: Bernard Tremblay <imaginasys@HOTMAIL.COM> Re: Audit tools (49 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> CHAID ResourcesCHAID Resources (12 lines) From: Brooks, Simon - CSG <Simon.Brooks@HAYSCSG.COM> Re: CHAID Resources (29 lines) From: Well Howell <whowell@SUPERLINK.NET> Re: CHAID Resources (40 lines) From: Roger DeAngelis <xlr82sas@AOL.COM> Re: CHAID Resources (16 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Can range be controlled in a N(0,1) distribution?Can range be controlled in a N(0,1) distribution? (165 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (58 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Can range be controlled in a N(0,1) distribution? (64 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (40 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Change in Mixed languageChange in Mixed language (51 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (67 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (137 lines) From: Rodney Sparapani <rsparapa@MCW.EDU> Re: Change in Mixed language (22 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (23 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Combine two filesCombine two files (35 lines) From: Graeme Kirton <gkirton@FILCS.COM> Re: Combine two files (20 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Combine two files (81 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Any way to embed the sas code inside the data setAny way to embed the sas code inside the data set (15 lines) From: pAyp <pauladx@HOME.COM> Re: Any way to embed the sas code inside the data set (38 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Any way to embed the sas code inside the data set (25 lines) From: Kevin Elliott <kevinelliott@HOTMAIL.COM> Re: Any way to embed the sas code inside the data set (27 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> Re: Any way to embed the sas code inside the data set (31 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Any way to embed the sas code inside the data set (30 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Any way to embed the sas code inside the data set (44 lines) From: pAyp <pauladx@HOME.COM> Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099)Re: Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099) (85 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Are you a foreign resident? 353834Are you a foreign resident? 353834 (61 lines) From: mike2343@btinternet.com <mike2343@BTINTERNET.COM> Audit toolsAudit tools (37 lines) From: Bernard Tremblay <imaginasys@HOTMAIL.COM> Re: Audit tools (49 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> CHAID ResourcesCHAID Resources (12 lines) From: Brooks, Simon - CSG <Simon.Brooks@HAYSCSG.COM> Re: CHAID Resources (29 lines) From: Well Howell <whowell@SUPERLINK.NET> Re: CHAID Resources (40 lines) From: Roger DeAngelis <xlr82sas@AOL.COM> Re: CHAID Resources (16 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Can range be controlled in a N(0,1) distribution?Can range be controlled in a N(0,1) distribution? (165 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (58 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Can range be controlled in a N(0,1) distribution? (64 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (40 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Change in Mixed languageChange in Mixed language (51 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (67 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (137 lines) From: Rodney Sparapani <rsparapa@MCW.EDU> Re: Change in Mixed language (22 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (23 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Combine two filesCombine two files (35 lines) From: Graeme Kirton <gkirton@FILCS.COM> Re: Combine two files (20 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Combine two files (81 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099)Re: Any way to embed the sas code inside the data setSAS-L Digest - 26 Aug 2001 to 27 Aug 2001 (#2001-1099) (85 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Are you a foreign resident? 353834Are you a foreign resident? 353834 (61 lines) From: mike2343@btinternet.com <mike2343@BTINTERNET.COM> Audit toolsAudit tools (37 lines) From: Bernard Tremblay <imaginasys@HOTMAIL.COM> Re: Audit tools (49 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> CHAID ResourcesCHAID Resources (12 lines) From: Brooks, Simon - CSG <Simon.Brooks@HAYSCSG.COM> Re: CHAID Resources (29 lines) From: Well Howell <whowell@SUPERLINK.NET> Re: CHAID Resources (40 lines) From: Roger DeAngelis <xlr82sas@AOL.COM> Re: CHAID Resources (16 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Can range be controlled in a N(0,1) distribution?Can range be controlled in a N(0,1) distribution? (165 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (58 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Can range be controlled in a N(0,1) distribution? (64 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (40 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Change in Mixed languageChange in Mixed language (51 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (67 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (137 lines) From: Rodney Sparapani <rsparapa@MCW.EDU> Re: Change in Mixed language (22 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (23 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Combine two filesCombine two files (35 lines) From: Graeme Kirton <gkirton@FILCS.COM> Re: Combine two files (20 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Combine two files (81 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Are you a foreign resident? 353834Are you a foreign resident? 353834 (61 lines) From: mike2343@btinternet.com <mike2343@BTINTERNET.COM> Audit toolsAudit tools (37 lines) From: Bernard Tremblay <imaginasys@HOTMAIL.COM> Re: Audit tools (49 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> CHAID ResourcesCHAID Resources (12 lines) From: Brooks, Simon - CSG <Simon.Brooks@HAYSCSG.COM> Re: CHAID Resources (29 lines) From: Well Howell <whowell@SUPERLINK.NET> Re: CHAID Resources (40 lines) From: Roger DeAngelis <xlr82sas@AOL.COM> Re: CHAID Resources (16 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Can range be controlled in a N(0,1) distribution?Can range be controlled in a N(0,1) distribution? (165 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (58 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Can range be controlled in a N(0,1) distribution? (64 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (40 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Change in Mixed languageChange in Mixed language (51 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (67 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (137 lines) From: Rodney Sparapani <rsparapa@MCW.EDU> Re: Change in Mixed language (22 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (23 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Combine two filesCombine two files (35 lines) From: Graeme Kirton <gkirton@FILCS.COM> Re: Combine two files (20 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Combine two files (81 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Audit toolsAudit tools (37 lines) From: Bernard Tremblay <imaginasys@HOTMAIL.COM> Re: Audit tools (49 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> CHAID ResourcesCHAID Resources (12 lines) From: Brooks, Simon - CSG <Simon.Brooks@HAYSCSG.COM> Re: CHAID Resources (29 lines) From: Well Howell <whowell@SUPERLINK.NET> Re: CHAID Resources (40 lines) From: Roger DeAngelis <xlr82sas@AOL.COM> Re: CHAID Resources (16 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Can range be controlled in a N(0,1) distribution?Can range be controlled in a N(0,1) distribution? (165 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (58 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Can range be controlled in a N(0,1) distribution? (64 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (40 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Change in Mixed languageChange in Mixed language (51 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (67 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (137 lines) From: Rodney Sparapani <rsparapa@MCW.EDU> Re: Change in Mixed language (22 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (23 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Combine two filesCombine two files (35 lines) From: Graeme Kirton <gkirton@FILCS.COM> Re: Combine two files (20 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Combine two files (81 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
CHAID ResourcesCHAID Resources (12 lines) From: Brooks, Simon - CSG <Simon.Brooks@HAYSCSG.COM> Re: CHAID Resources (29 lines) From: Well Howell <whowell@SUPERLINK.NET> Re: CHAID Resources (40 lines) From: Roger DeAngelis <xlr82sas@AOL.COM> Re: CHAID Resources (16 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Can range be controlled in a N(0,1) distribution?Can range be controlled in a N(0,1) distribution? (165 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (58 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Can range be controlled in a N(0,1) distribution? (64 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (40 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Change in Mixed languageChange in Mixed language (51 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (67 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (137 lines) From: Rodney Sparapani <rsparapa@MCW.EDU> Re: Change in Mixed language (22 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (23 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Combine two filesCombine two files (35 lines) From: Graeme Kirton <gkirton@FILCS.COM> Re: Combine two files (20 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Combine two files (81 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Can range be controlled in a N(0,1) distribution?Can range be controlled in a N(0,1) distribution? (165 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (58 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Can range be controlled in a N(0,1) distribution? (64 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Can range be controlled in a N(0,1) distribution? (40 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Change in Mixed languageChange in Mixed language (51 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (67 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (137 lines) From: Rodney Sparapani <rsparapa@MCW.EDU> Re: Change in Mixed language (22 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (23 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Combine two filesCombine two files (35 lines) From: Graeme Kirton <gkirton@FILCS.COM> Re: Combine two files (20 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Combine two files (81 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Change in Mixed languageChange in Mixed language (51 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (67 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (137 lines) From: Rodney Sparapani <rsparapa@MCW.EDU> Re: Change in Mixed language (22 lines) From: Michael Babyak <mbabyak@DUKE.EDU> Re: Change in Mixed language (23 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Combine two filesCombine two files (35 lines) From: Graeme Kirton <gkirton@FILCS.COM> Re: Combine two files (20 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Combine two files (81 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Combine two filesCombine two files (35 lines) From: Graeme Kirton <gkirton@FILCS.COM> Re: Combine two files (20 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Combine two files (81 lines) From: David Johnson <DavidJohnson@HALIFAX.CO.UK> Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Converting SAS sparse format data to MPS formatConverting SAS sparse format data to MPS format (28 lines) From: Richard Williamson <r4willi@WAL-MART.COM> Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Dates on between not working?Dates on between not working? (33 lines) From: Steve <guitarzealot@YAHOO.COM> Re: Dates on between not working? (48 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Dates on between not working? (65 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: Dates on between not working? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Detecting a corrupted sas datasetDetecting a corrupted sas dataset (35 lines) From: Stanley Fogleman <stfogleman@NETSCAPE.NET> EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
EXPLORER/NOEXPLOREREXPLORER/NOEXPLORER (46 lines) From: Eric Wajnberg <wajnberg@ANTIBES.INRA.FR> Re: EXPLORER/NOEXPLORER (66 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Enterprise GuideRe: Enterprise Guide (44 lines) From: Stephen T. Dziuban <sdziuban@QWEST.NET> Re: Enterprise Guide (55 lines) From: Eiko Kubo <eikokubo@YAHOO.COM> FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
FW: Please help... Basic dataset problemFW: Please help... Basic dataset problem (94 lines) From: Fazzino, Salvatore <sfazzino@FIRSTAM.COM> FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
FW: Where IS Language Reference in v8.1?FW: Where IS Language Reference in v8.1? (91 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Frequency Distribution in SAS.Frequency Distribution in SAS. (24 lines) From: balu <dearfolks@HOTMAIL.COM> Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Fwd: Multidimensional scalingFwd: Multidimensional scaling (109 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Good Unix-based search engine?Good Unix-based search engine? (18 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Good Unix-based search engine? (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (37 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Re: Good Unix-based search engine? (44 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (35 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Good Unix-based search engine? (62 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Good Unix-based search engine? (32 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Good Unix-based search engine? (27 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Help with Print PreviewHelp with Print Preview (20 lines) From: John N. <jnokes1@YAHOO.COM> Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Help with Print Preview (Unix)Re: Help with Print Preview (Unix) (80 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Help!: Starting in SASHelp!: Starting in SAS (16 lines) From: Carlos Palacios <carlospalacios@WANADOO.ES> Re: Help!: Starting in SAS (54 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: Help!: Starting in SAS (40 lines) From: wei cheng <cheng_wei@HOTMAIL.COM> Re: Help!: Starting in SAS (28 lines) From: Anne Jordan <Anne.Jordan@CHSPR.ORG> Re: Help!: Starting in SAS (23 lines) From: greg warnick <gwarnick@SNAP.FHCRC.ORG> Re: Help!: Starting in SAS (33 lines) From: Bas Pruijn <bas.pruijn@CMG.NL> Re: Help!: Starting in SAS (45 lines) From: tedphy <tedphy@YAHOO.COM> Re: Help!: Starting in SAS (41 lines) From: Jonathan Siegel <Jonathan.Siegel@PFIZER.COM> Re: Help!: Starting in SAS (40 lines) From: Charles Patridge <Charles_S_Patridge@PRODIGY.NET> Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Hex to decimal, or incrementing HEX numbersHex to decimal, or incrementing HEX numbers (60 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (49 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (88 lines) From: Hunley, Ike <Ike.Hunley@BCBSFL.COM> Re: Hex to decimal, or incrementing HEX numbers (164 lines) From: Kenneth Moody <KennethMoody@FIRSTHEALTH.COM> How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
How to assign a data step character value to a macro varHow to assign a data step character value to a macro var (49 lines) From: Robert Stewart <stewart_gris@HOTMAIL.COM> Re: How to assign a data step character value to a macro var (92 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: How to assign a data step character value to a macro var (84 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Insight problemInsight problem (39 lines) From: Aleksi Lehtonen <aleksi.lehtonen@METLA.FI> Re: Insight problem (52 lines) From: Smith, Curtis, Mr, DCAA <Curtis.Smith@DCAA.MIL> Re: Insight problem (64 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Interfacing SCL>SUBMIT block for multiple valuesInterfacing SCL>SUBMIT block for multiple values (45 lines) From: Clemens van Brunschot <c.vanbrunschot@CHELLO.NL> Re: Interfacing SCL>SUBMIT block for multiple values (45 lines) From: Jeff Voeller <c-Jeff.Voeller@WCOM.COM> Re: Interfacing SCL>SUBMIT block for multiple values (61 lines) From: David L. Ward <dward@SASHELP.COM> Re: Interfacing SCL>SUBMIT block for multiple values (62 lines) From: Cozy-C <cozy_c@HOTMAIL.COM> Re: Interfacing SCL>SUBMIT block for multiple values (78 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Iron SAS @ SSU 2001 - the First BattleIron SAS @ SSU 2001 - the First Battle (64 lines) From: S. David Riba <dave@JADETEK.COM> JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
JMP and SAS statJMP and SAS stat (20 lines) From: srinivas <sristatistician@YAHOO.COM> Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Latent Class AnalysisLatent Class Analysis (10 lines) From: Baumer, Eric P. <BaumerE@MSX.UMSL.EDU> Re: Latent Class Analysis (51 lines) From: John Jones <jonesj@PHARMARESEARCH.COM> Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Lightweight/ Agile Methodologies for Software DevelopmentLightweight/ Agile Methodologies for Software Development (122 lines) From: Barnes Nelson, Greg <greg.barnesnelson@STATPROBETECHNOLOGIES.COM> MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
MODULE failing to unload dll after data step in interactive SASMODULE failing to unload dll after data step in interactive SAS (46 lines) From: Francis Harvey <HARVEYF1@WESTAT.COM> Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Macro Variable resolutionMacro Variable resolution (230 lines) From: Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK> Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Macros and global variablesMacros and global variables (32 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (49 lines) From: kviel <kviel@GMCF.ORG> Re: Macros and global variables (92 lines) From: Terjeson, Mark <TerjeMW@DSHS.WA.GOV> Re: Macros and global variables (13 lines) From: Draschner, Eugenio A <eugenio.draschner@OTS.TREAS.GOV> Re: Macros and global variables (57 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Macros and global variables (99 lines) From: kviel <kviel@GMCF.ORG> NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
NESUG '01 registration - only 2 weeks leftNESUG '01 registration - only 2 weeks left (36 lines) From: Sue Douglass <douglass@BA.ARS.USDA.GOV> Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice)Re: Nettiquette: trim posts, don't post digest (was Re: Good Statistical Practice) (138 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
ODS PROC REPORT PDF BookmarksODS PROC REPORT PDF Bookmarks (31 lines) From: Don Hurst <hurst_don@ALLERGAN.COM> ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
ODS RTF v8.2: Bold in text in data _null_?ODS RTF v8.2: Bold in text in data _null_? (156 lines) From: Charles Kincaid <Chuck_Kincaid@TRILOGYUSA.COM> Re: ODS RTF v8.2: Bold in text in data _null_? (203 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
OT: Convert all worksheets in an Excel workbook to CSVOT: Convert all worksheets in an Excel workbook to CSV (27 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: OT: Convert all worksheets in an Excel workbook to CSV (47 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
OT: FIM: Brain-Inspired ComputingOT: FIM: Brain-Inspired Computing (113 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
PCA for DummiesPCA for Dummies (51 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> Re: PCA for Dummies (51 lines) From: David L. Cassell <Cassell.David@EPAMAIL.EPA.GOV> PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
PCA for dummies - summaryPCA for dummies - summary (80 lines) From: Michael A O Ash <mash@ECONS.UMASS.EDU> PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
PROC EXPORT and formatsPROC EXPORT and formats (13 lines) From: Paul Thompson <paul@WUBIOS.WUSTL.EDU> Re: PROC EXPORT and formats (108 lines) From: Edward Heaton <HEATONE@WESTAT.COM> PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
PROC REG, backward elimination, model not full rankPROC REG, backward elimination, model not full rank (29 lines) From: Abelson_R <Abelson_R@BLS.GOV> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (75 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: PROC REG, backward elimination, model not full rank (25 lines) From: Seymour Douglas <seymour.d.douglas@ACCENTURE.COM> Re: PROC REG, backward elimination, model not full rank (100 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
PROC REPORT - Bug or FeaturePROC REPORT - Bug or Feature (28 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: PROC REPORT - Bug or Feature (63 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (26 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (73 lines) From: DeShon, Joe <jdesho01@SPRINTSPECTRUM.COM> Re: PROC REPORT - Bug or Feature (100 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Re: PROC REPORT - Bug or Feature (112 lines) From: Pete Lund <pete.lund@NWCSR.COM> Re: PROC REPORT - Bug or Feature (59 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
PROC REPORT woesPROC REPORT woes (20 lines) From: Wanda Upole <wupole@KAI-RESEARCH.COM> Re: PROC REPORT woes (44 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Please help... Basic dataset problemPlease help... Basic dataset problem (42 lines) From: Wil <affd3@YAHOO.COM> Re: Please help... Basic dataset problem (56 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Please help... Basic dataset problem (57 lines) From: Doc Muhlbaier <lawrence.muhlbaier@DUKE.EDU> Re: Please help... Basic dataset problem (47 lines) From: Arthur Tabachneck <atabachneck@HOME.COM> Re: Please help... Basic dataset problem (99 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (55 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (66 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (48 lines) From: Dianne Rhodes <RHODESD1@WESTAT.COM> Re: Please help... Basic dataset problem (49 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (45 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (67 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (118 lines) From: Ian Whitlock <WHITLOI1@WESTAT.COM> Re: Please help... Basic dataset problem (67 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Re: Please help... Basic dataset problem (51 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (60 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: Please help... Basic dataset problem (78 lines) From: Ace <b.rogers@VIRGIN.NET> Re: Please help... Basic dataset problem (56 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Position Available/SAS Programmer/NYPosition Available/SAS Programmer/NY (49 lines) From: Bill Christison <knowltongroup@YAHOO.COM> Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Postscript output from Pareto under Unix SAS?Postscript output from Pareto under Unix SAS? (103 lines) From: Kenny Gross <kenny.gross@SUN.COM> Re: Postscript output from Pareto under Unix SAS? (124 lines) From: Droogendyk Bill <bill_droogendyk@DOFASCO.CA> Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Predefined format?Predefined format? (12 lines) From: Simon <simpabimpa@HOTMAIL.COM> Re: Predefined format? (42 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Problem with PROC TRANSPOSEProblem with PROC TRANSPOSE (36 lines) From: Paula Sims <paula_sims00@HOTMAIL.COM> Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Problem with page dimension text in PROC TABULATEProblem with page dimension text in PROC TABULATE (41 lines) From: Christoph Helwig <Christoph.Helwig@QUINTILES.COM> Re: Problem with page dimension text in PROC TABULATE (62 lines) From: Braten, Michael (Exchange) <mbraten@BEAR.COM> Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Proc Mixed Info about model fitting for repeated measuresProc Mixed Info about model fitting for repeated measures (22 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (29 lines) From: hngrad <hngrad@HUMEC.KSU.EDU> Re: Proc Mixed Info about model fitting for repeated measures (78 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Proc compare and floating point differencesProc compare and floating point differences (50 lines) From: Nick Paszty <paszty@XOMA.COM> Re: Proc compare and floating point differences (38 lines) From: Steven Dubnoff <sdubnoff@CIRCLESYS.COM> Re: Proc compare and floating point differences (61 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Q to improve code using MacrosQ to improve code using Macros (58 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (97 lines) From: Tribius, Heide <Heide.Tribius@KFW.DE> Re: Q to improve code using Macros (116 lines) From: RAHUL CHAHAL <rahulchahal@YAHOO.COM> Re: Q to improve code using Macros (96 lines) From: Diskin, Dennis <Dennis.Diskin@PHARMA.COM> Re: Q to improve code using Macros (310 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Q to improve code using Macros (83 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Q: Easiest way to drop all-missing variables: Help with SYMGE TRe: Q: Easiest way to drop all-missing variables: Help with SYMGE T (96 lines) From: Torben Skov <tosko@TDC.DK> Re: Q: Easiest way to drop all-missing variables: Help with SYMGE T (25 lines) From: kviel <kviel@GMCF.ORG> Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Q: Easiest way to drop all-missing variables: Help with SYMGETRe: Q: Easiest way to drop all-missing variables: Help with SYMGET (91 lines) From: Amy Roehrig Swinford <aimless@FIBER.NET> Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Q: in PROC IMPORT, HOW TO in/format variablesQ: in PROC IMPORT, HOW TO in/format variables (58 lines) From: Qiang Ling <qling@SCHOOLPH.UMASS.EDU> Re: Q: in PROC IMPORT, HOW TO in/format variables (25 lines) From: Dezainde, Francois <francois.dezainde@BELL.CA> RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
RUN; statements, etc. (nee: PROC REPORT - Bug or Feature)RUN; statements, etc. (nee: PROC REPORT - Bug or Feature) (141 lines) From: Ray Pass <raypass@ATT.NET> Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Reading 8millions record OracleRe: Reading 8millions record Oracle (31 lines) From: Serguei Ishchenko <sishchen@PRAIRIENET.ORG> Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Reading a CSV FileReading a CSV File (44 lines) From: Wang, Zhaoping (USPC Marketing & Investments Division) <ZWang@NA2.US.ML.COM> Re: Reading a CSV File (57 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Reading a CSV File (84 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: Reading a CSV File (161 lines) From: Peter Crawford <peter.crawford@DB.COM> Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Reducing run timeReducing run time (36 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (56 lines) From: Patrice Bourdages <patrice.bourdages@VIDEOTRON.CA> Re: Reducing run time (74 lines) From: Richard DeVenezia <radevenz@IX.NETCOM.COM> Re: Reducing run time (57 lines) From: Brad Goldman <Brad.Goldman@AUTOTRADER.COM> Re: Reducing run time (14 lines) From: Robert Nehez <rnez@MEMO.IKEA.COM> Re: Reducing run time (28 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Reformatting DatesReformatting Dates (17 lines) From: Elizabeth Marshall <Elizabeth.Marshall@HEALTH.UTAH.EDU> Re: Reformatting Dates (59 lines) From: Nat Wooding <Nathaniel_Wooding@DOM.COM> Re: Reformatting Dates (105 lines) From: Edward Heaton <HEATONE@WESTAT.COM> Re: Reformatting Dates (286 lines) From: Bill Knowlton <Bill_Knowlton@BAXTER.COM> Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Richmond VA SAS(r) Software Training Seminars in SeptemberRichmond VA SAS(r) Software Training Seminars in September (48 lines) From: Andrew H. Karp <sfbay0001@AOL.COMNOSPAM> Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
Running a SAS job from within another?Running a SAS job from within another? (36 lines) From: E. S. <sasq98@YAHOO.COM> Re: Running a SAS job from within another? (47 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: Running a SAS job from within another? (51 lines) From: Aldi Kraja <aldi@WUBIOS.WUSTL.EDU> Re: Running a SAS job from within another? (159 lines) From: Huang, Ya <ya.huang@AGOURON.COM> Re: Running a SAS job from within another? (212 lines) From: Mike Durbin <mdurbin@ERAC.COM> Re: Running a SAS job from within another? (58 lines) From: Pete Welbrock <welbrock@EROLS.COM> Re: Running a SAS job from within another? (96 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: Running a SAS job from within another? (24 lines) From: Fred Swisher <freds@NOADDRESS.COM> Re: Running a SAS job from within another? (50 lines) From: Echo Liu <liue2@TDBANK.CA> Re: Running a SAS job from within another? (23 lines) From: Jonathan Goldberg <jonathan@MATLOCK.WUSTL.EDU> Re: Running a SAS job from within another? (84 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SASSAS (38 lines) From: SMCI <info@SMCI.COM> SAS (60 lines) From: SMCI <info@SMCI.COM> SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SAS Connect to OracleSAS Connect to Oracle (23 lines) From: Terry Fudin <t.fudin@GENAISSANCE.COM> SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SAS Licensing Policy, was Re: let's start a user revolt against sas/connectSAS Licensing Policy, was Re: let's start a user revolt against sas/connect (58 lines) From: don.henderson@US.PWCGLOBAL.COM Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (31 lines) From: Newbie JrSysAdmin <utlonghornsrule@YAHOO.COM> Re: SAS Licensing Policy, was Re: let's start a user revolt against sas/connect (78 lines) From: John Whittington <John.W@MEDISCIENCE.CO.UK> SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SAS Opportunity in Baltimore, MarylandSAS Opportunity in Baltimore, Maryland (47 lines) From: Helen-Jean Talbott <HJTalbott@WORLDNET.ATT.NET> SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SAS Programmer Position Available-Buffalo,NYSAS Programmer Position Available-Buffalo,NY (71 lines) From: Kathleen Reitz <kathleen.reitz@COGNIGENCORP.COM> SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SAS R8.2 Problem (0C1) on MVSSAS R8.2 Problem (0C1) on MVS (39 lines) From: Osama Keshtah <osama_keshtah@ALFALAK.COM> Re: SAS R8.2 Problem (0C1) on MVS (44 lines) From: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE> SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SAS View file - It it posible to update it?SAS View file - It it posible to update it? (17 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> Re: SAS View file - It it posible to update it? (50 lines) From: Dale McLerran <dmclerra@MY-DEJA.COM> Re: SAS View file - It it posible to update it? (40 lines) From: Sigurd Hermansen <hermans1@WESTAT.COM> Re: SAS View file - It it posible to update it? (63 lines) From: Shiferaw_G <Shiferaw_G@BLS.GOV> SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SAS WEB EIS FIREWALL SECURITY??SAS WEB EIS FIREWALL SECURITY?? (47 lines) From: Bill Doherty <bdoherty@PRIMETHERAPEUTICS.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (153 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Bill Dvorak <bdvorak@YAHOO.COM> Re: SAS WEB EIS FIREWALL SECURITY?? (41 lines) From: Jack Hamilton <JackHamilton@FIRSTHEALTH.COM> SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SAS certified professional examSAS certified professional exam (17 lines) From: tedphy <tedphy@YAHOO.COM> SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SAS command to make directories in windows envt?SAS command to make directories in windows envt? (15 lines) From: Peter Larsen <phlarsen@YAHOO.COM> Re: SAS command to make directories in windows envt? (50 lines) From: Fred Gehm <fred.x.gehm@HOUSEHOLD.COM> Re: SAS command to make directories in windows envt? (36 lines) From: Bart Heinsius <Bart.Heinsius@EOMDATA.NL> Re: SAS command to make directories in windows envt? (28 lines) From: Krzy¶ O Poranku <KrzysoPoranku@POCZTA.ONET.PL> SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SAS on Alpha UNIXSAS on Alpha UNIX (38 lines) From: Nick Paszty <paszty@XOMA.COM> Re: SAS on Alpha UNIX (52 lines) From: William W. Viergever <wwvierg@ATTGLOBAL.NET> Re: SAS on Alpha UNIX (128 lines) From: Karsten M. Self <kmself@IX.NETCOM.COM> Re: SAS on Alpha UNIX (131 lines) From: Gregg P. Snell <gsnell@DATASAVANTCONSULTING.COM> Re: SAS on Alpha UNIX (76 lines) From: George Chalissery <chalissery@HOTMAIL.COM> Re: SAS on Alpha UNIX (111 lines) From: Jim Agnew <agnew@HSC.VCU.EDU> SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SAS on OS/390: Call external pgm, pass low values in PARM?SAS on OS/390: Call external pgm, pass low values in PARM? (68 lines) From: Larry Bertolini <bertolini.1@OSU.EDU> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (95 lines) From: Dorfman, Paul <Paul.Dorfman@BCBSFL.COM> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: Peter Crawford <Peter@CRAWFORDSOFTWARE.DEMON.CO.UK> Re: SAS on OS/390: Call external pgm, pass low values in PARM? (116 lines) From: M@M.COM SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SAS programmer/analyst availableSAS programmer/analyst available (9 lines) From: tchabot@DDS.UGA.EDU SAS to Excel with Headings on multiple lines
SAS to Excel with Headings on multiple lines