'ROMANCE'... God's greatest gift........'ROMANCE'... God's greatest gift........ (20 lines) From: Barathi <jayabarathi2007@GMAIL.COM> (Paul) Group size & mixed model (binary resp)Re: (Paul) Group size & mixed model (binary resp) (24 lines) From: Susan Lingle <susan.lingle@ULETH.CA> 76100378757610037875 (361 lines) From: Frank Mwaniki <fmwaniki@GHX.COM> ? format related problem_inputRe: ? format related problem_input (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> A SAS IRC channelA SAS IRC channel (28 lines) From: Laurent VALDES <laurent@LE-VALDO.COM> Re: A SAS IRC channel (49 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: A SAS IRC channel (74 lines) From: Laurent Valdes <valderama@GMAIL.COM> Re: A SAS IRC channel (36 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> A SAS-L Thank YouA SAS-L Thank You (35 lines) From: Catley, Dennis <dcatley@EXCHANGE.VT.EDU> A graph in a web page interactive with the server?A graph in a web page interactive with the server? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A graph in a web page interactive with the server? (51 lines) From: Don Henderson <donaldjhenderson@HOTMAIL.COM> Re: A graph in a web page interactive with the server? (79 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Any hardware gurus? SAS config questionRe: Any hardware gurus? SAS config question (84 lines) From: Phil Holland <news@HOLLANDNUMERICS.COM> Auto data type conversion in Datastep-SQLAuto data type conversion in Datastep-SQL (41 lines) From: LV Subbu <lvsubboo@GMAIL.COM> Re: Auto data type conversion in Datastep-SQL (77 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: Auto data type conversion in Datastep-SQL (89 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Auto data type conversion in Datastep-SQL (66 lines) From: Tom Hide <tom.hide@DEHIWORLD.COM> Best way to find unusual observationsBest way to find unusual observations (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (46 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (59 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (64 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (64 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (99 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Best way to find unusual observations (85 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Best way to find unusual observations (74 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (151 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Brain freeze: informat to read text "December 31, 2007"Brain freeze: informat to read text "December 31, 2007" (17 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Brain freeze: informat to read text "December 31, 2007" (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Brain freeze: informat to read text "December 31, 2007" (28 lines) From: Dave Scocca <dave@SCOCCA.ORG> Re: Brain freeze: informat to read text "December 31, 2007" (31 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Business ShopBusiness Shop (106 lines) From: Goteborgbank <cwmbanker@GMAIL.COM> Can I create a SAS program that prompts the user for input?Can I create a SAS program that prompts the user for input? (18 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: Can I create a SAS program that prompts the user for input? (44 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
(Paul) Group size & mixed model (binary resp)Re: (Paul) Group size & mixed model (binary resp) (24 lines) From: Susan Lingle <susan.lingle@ULETH.CA> 76100378757610037875 (361 lines) From: Frank Mwaniki <fmwaniki@GHX.COM> ? format related problem_inputRe: ? format related problem_input (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> A SAS IRC channelA SAS IRC channel (28 lines) From: Laurent VALDES <laurent@LE-VALDO.COM> Re: A SAS IRC channel (49 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: A SAS IRC channel (74 lines) From: Laurent Valdes <valderama@GMAIL.COM> Re: A SAS IRC channel (36 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> A SAS-L Thank YouA SAS-L Thank You (35 lines) From: Catley, Dennis <dcatley@EXCHANGE.VT.EDU> A graph in a web page interactive with the server?A graph in a web page interactive with the server? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A graph in a web page interactive with the server? (51 lines) From: Don Henderson <donaldjhenderson@HOTMAIL.COM> Re: A graph in a web page interactive with the server? (79 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Any hardware gurus? SAS config questionRe: Any hardware gurus? SAS config question (84 lines) From: Phil Holland <news@HOLLANDNUMERICS.COM> Auto data type conversion in Datastep-SQLAuto data type conversion in Datastep-SQL (41 lines) From: LV Subbu <lvsubboo@GMAIL.COM> Re: Auto data type conversion in Datastep-SQL (77 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: Auto data type conversion in Datastep-SQL (89 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Auto data type conversion in Datastep-SQL (66 lines) From: Tom Hide <tom.hide@DEHIWORLD.COM> Best way to find unusual observationsBest way to find unusual observations (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (46 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (59 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (64 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (64 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (99 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Best way to find unusual observations (85 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Best way to find unusual observations (74 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (151 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Brain freeze: informat to read text "December 31, 2007"Brain freeze: informat to read text "December 31, 2007" (17 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Brain freeze: informat to read text "December 31, 2007" (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Brain freeze: informat to read text "December 31, 2007" (28 lines) From: Dave Scocca <dave@SCOCCA.ORG> Re: Brain freeze: informat to read text "December 31, 2007" (31 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Business ShopBusiness Shop (106 lines) From: Goteborgbank <cwmbanker@GMAIL.COM> Can I create a SAS program that prompts the user for input?Can I create a SAS program that prompts the user for input? (18 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: Can I create a SAS program that prompts the user for input? (44 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
76100378757610037875 (361 lines) From: Frank Mwaniki <fmwaniki@GHX.COM> ? format related problem_inputRe: ? format related problem_input (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> A SAS IRC channelA SAS IRC channel (28 lines) From: Laurent VALDES <laurent@LE-VALDO.COM> Re: A SAS IRC channel (49 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: A SAS IRC channel (74 lines) From: Laurent Valdes <valderama@GMAIL.COM> Re: A SAS IRC channel (36 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> A SAS-L Thank YouA SAS-L Thank You (35 lines) From: Catley, Dennis <dcatley@EXCHANGE.VT.EDU> A graph in a web page interactive with the server?A graph in a web page interactive with the server? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A graph in a web page interactive with the server? (51 lines) From: Don Henderson <donaldjhenderson@HOTMAIL.COM> Re: A graph in a web page interactive with the server? (79 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Any hardware gurus? SAS config questionRe: Any hardware gurus? SAS config question (84 lines) From: Phil Holland <news@HOLLANDNUMERICS.COM> Auto data type conversion in Datastep-SQLAuto data type conversion in Datastep-SQL (41 lines) From: LV Subbu <lvsubboo@GMAIL.COM> Re: Auto data type conversion in Datastep-SQL (77 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: Auto data type conversion in Datastep-SQL (89 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Auto data type conversion in Datastep-SQL (66 lines) From: Tom Hide <tom.hide@DEHIWORLD.COM> Best way to find unusual observationsBest way to find unusual observations (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (46 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (59 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (64 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (64 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (99 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Best way to find unusual observations (85 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Best way to find unusual observations (74 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (151 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Brain freeze: informat to read text "December 31, 2007"Brain freeze: informat to read text "December 31, 2007" (17 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Brain freeze: informat to read text "December 31, 2007" (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Brain freeze: informat to read text "December 31, 2007" (28 lines) From: Dave Scocca <dave@SCOCCA.ORG> Re: Brain freeze: informat to read text "December 31, 2007" (31 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Business ShopBusiness Shop (106 lines) From: Goteborgbank <cwmbanker@GMAIL.COM> Can I create a SAS program that prompts the user for input?Can I create a SAS program that prompts the user for input? (18 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: Can I create a SAS program that prompts the user for input? (44 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
? format related problem_inputRe: ? format related problem_input (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> A SAS IRC channelA SAS IRC channel (28 lines) From: Laurent VALDES <laurent@LE-VALDO.COM> Re: A SAS IRC channel (49 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: A SAS IRC channel (74 lines) From: Laurent Valdes <valderama@GMAIL.COM> Re: A SAS IRC channel (36 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> A SAS-L Thank YouA SAS-L Thank You (35 lines) From: Catley, Dennis <dcatley@EXCHANGE.VT.EDU> A graph in a web page interactive with the server?A graph in a web page interactive with the server? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A graph in a web page interactive with the server? (51 lines) From: Don Henderson <donaldjhenderson@HOTMAIL.COM> Re: A graph in a web page interactive with the server? (79 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Any hardware gurus? SAS config questionRe: Any hardware gurus? SAS config question (84 lines) From: Phil Holland <news@HOLLANDNUMERICS.COM> Auto data type conversion in Datastep-SQLAuto data type conversion in Datastep-SQL (41 lines) From: LV Subbu <lvsubboo@GMAIL.COM> Re: Auto data type conversion in Datastep-SQL (77 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: Auto data type conversion in Datastep-SQL (89 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Auto data type conversion in Datastep-SQL (66 lines) From: Tom Hide <tom.hide@DEHIWORLD.COM> Best way to find unusual observationsBest way to find unusual observations (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (46 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (59 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (64 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (64 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (99 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Best way to find unusual observations (85 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Best way to find unusual observations (74 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (151 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Brain freeze: informat to read text "December 31, 2007"Brain freeze: informat to read text "December 31, 2007" (17 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Brain freeze: informat to read text "December 31, 2007" (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Brain freeze: informat to read text "December 31, 2007" (28 lines) From: Dave Scocca <dave@SCOCCA.ORG> Re: Brain freeze: informat to read text "December 31, 2007" (31 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Business ShopBusiness Shop (106 lines) From: Goteborgbank <cwmbanker@GMAIL.COM> Can I create a SAS program that prompts the user for input?Can I create a SAS program that prompts the user for input? (18 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: Can I create a SAS program that prompts the user for input? (44 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
A SAS IRC channelA SAS IRC channel (28 lines) From: Laurent VALDES <laurent@LE-VALDO.COM> Re: A SAS IRC channel (49 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: A SAS IRC channel (74 lines) From: Laurent Valdes <valderama@GMAIL.COM> Re: A SAS IRC channel (36 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> A SAS-L Thank YouA SAS-L Thank You (35 lines) From: Catley, Dennis <dcatley@EXCHANGE.VT.EDU> A graph in a web page interactive with the server?A graph in a web page interactive with the server? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A graph in a web page interactive with the server? (51 lines) From: Don Henderson <donaldjhenderson@HOTMAIL.COM> Re: A graph in a web page interactive with the server? (79 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Any hardware gurus? SAS config questionRe: Any hardware gurus? SAS config question (84 lines) From: Phil Holland <news@HOLLANDNUMERICS.COM> Auto data type conversion in Datastep-SQLAuto data type conversion in Datastep-SQL (41 lines) From: LV Subbu <lvsubboo@GMAIL.COM> Re: Auto data type conversion in Datastep-SQL (77 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: Auto data type conversion in Datastep-SQL (89 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Auto data type conversion in Datastep-SQL (66 lines) From: Tom Hide <tom.hide@DEHIWORLD.COM> Best way to find unusual observationsBest way to find unusual observations (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (46 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (59 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (64 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (64 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (99 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Best way to find unusual observations (85 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Best way to find unusual observations (74 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (151 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Brain freeze: informat to read text "December 31, 2007"Brain freeze: informat to read text "December 31, 2007" (17 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Brain freeze: informat to read text "December 31, 2007" (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Brain freeze: informat to read text "December 31, 2007" (28 lines) From: Dave Scocca <dave@SCOCCA.ORG> Re: Brain freeze: informat to read text "December 31, 2007" (31 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Business ShopBusiness Shop (106 lines) From: Goteborgbank <cwmbanker@GMAIL.COM> Can I create a SAS program that prompts the user for input?Can I create a SAS program that prompts the user for input? (18 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: Can I create a SAS program that prompts the user for input? (44 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
A SAS-L Thank YouA SAS-L Thank You (35 lines) From: Catley, Dennis <dcatley@EXCHANGE.VT.EDU> A graph in a web page interactive with the server?A graph in a web page interactive with the server? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A graph in a web page interactive with the server? (51 lines) From: Don Henderson <donaldjhenderson@HOTMAIL.COM> Re: A graph in a web page interactive with the server? (79 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Any hardware gurus? SAS config questionRe: Any hardware gurus? SAS config question (84 lines) From: Phil Holland <news@HOLLANDNUMERICS.COM> Auto data type conversion in Datastep-SQLAuto data type conversion in Datastep-SQL (41 lines) From: LV Subbu <lvsubboo@GMAIL.COM> Re: Auto data type conversion in Datastep-SQL (77 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: Auto data type conversion in Datastep-SQL (89 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Auto data type conversion in Datastep-SQL (66 lines) From: Tom Hide <tom.hide@DEHIWORLD.COM> Best way to find unusual observationsBest way to find unusual observations (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (46 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (59 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (64 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (64 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (99 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Best way to find unusual observations (85 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Best way to find unusual observations (74 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (151 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Brain freeze: informat to read text "December 31, 2007"Brain freeze: informat to read text "December 31, 2007" (17 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Brain freeze: informat to read text "December 31, 2007" (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Brain freeze: informat to read text "December 31, 2007" (28 lines) From: Dave Scocca <dave@SCOCCA.ORG> Re: Brain freeze: informat to read text "December 31, 2007" (31 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Business ShopBusiness Shop (106 lines) From: Goteborgbank <cwmbanker@GMAIL.COM> Can I create a SAS program that prompts the user for input?Can I create a SAS program that prompts the user for input? (18 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: Can I create a SAS program that prompts the user for input? (44 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
A graph in a web page interactive with the server?A graph in a web page interactive with the server? (21 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: A graph in a web page interactive with the server? (51 lines) From: Don Henderson <donaldjhenderson@HOTMAIL.COM> Re: A graph in a web page interactive with the server? (79 lines) From: Huang, Ya <Ya.Huang@AMYLIN.COM> Any hardware gurus? SAS config questionRe: Any hardware gurus? SAS config question (84 lines) From: Phil Holland <news@HOLLANDNUMERICS.COM> Auto data type conversion in Datastep-SQLAuto data type conversion in Datastep-SQL (41 lines) From: LV Subbu <lvsubboo@GMAIL.COM> Re: Auto data type conversion in Datastep-SQL (77 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: Auto data type conversion in Datastep-SQL (89 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Auto data type conversion in Datastep-SQL (66 lines) From: Tom Hide <tom.hide@DEHIWORLD.COM> Best way to find unusual observationsBest way to find unusual observations (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (46 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (59 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (64 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (64 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (99 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Best way to find unusual observations (85 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Best way to find unusual observations (74 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (151 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Brain freeze: informat to read text "December 31, 2007"Brain freeze: informat to read text "December 31, 2007" (17 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Brain freeze: informat to read text "December 31, 2007" (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Brain freeze: informat to read text "December 31, 2007" (28 lines) From: Dave Scocca <dave@SCOCCA.ORG> Re: Brain freeze: informat to read text "December 31, 2007" (31 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Business ShopBusiness Shop (106 lines) From: Goteborgbank <cwmbanker@GMAIL.COM> Can I create a SAS program that prompts the user for input?Can I create a SAS program that prompts the user for input? (18 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: Can I create a SAS program that prompts the user for input? (44 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Any hardware gurus? SAS config questionRe: Any hardware gurus? SAS config question (84 lines) From: Phil Holland <news@HOLLANDNUMERICS.COM> Auto data type conversion in Datastep-SQLAuto data type conversion in Datastep-SQL (41 lines) From: LV Subbu <lvsubboo@GMAIL.COM> Re: Auto data type conversion in Datastep-SQL (77 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: Auto data type conversion in Datastep-SQL (89 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Auto data type conversion in Datastep-SQL (66 lines) From: Tom Hide <tom.hide@DEHIWORLD.COM> Best way to find unusual observationsBest way to find unusual observations (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (46 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (59 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (64 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (64 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (99 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Best way to find unusual observations (85 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Best way to find unusual observations (74 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (151 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Brain freeze: informat to read text "December 31, 2007"Brain freeze: informat to read text "December 31, 2007" (17 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Brain freeze: informat to read text "December 31, 2007" (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Brain freeze: informat to read text "December 31, 2007" (28 lines) From: Dave Scocca <dave@SCOCCA.ORG> Re: Brain freeze: informat to read text "December 31, 2007" (31 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Business ShopBusiness Shop (106 lines) From: Goteborgbank <cwmbanker@GMAIL.COM> Can I create a SAS program that prompts the user for input?Can I create a SAS program that prompts the user for input? (18 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: Can I create a SAS program that prompts the user for input? (44 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Auto data type conversion in Datastep-SQLAuto data type conversion in Datastep-SQL (41 lines) From: LV Subbu <lvsubboo@GMAIL.COM> Re: Auto data type conversion in Datastep-SQL (77 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: Auto data type conversion in Datastep-SQL (89 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Auto data type conversion in Datastep-SQL (66 lines) From: Tom Hide <tom.hide@DEHIWORLD.COM> Best way to find unusual observationsBest way to find unusual observations (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (46 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (59 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (64 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (64 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (99 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Best way to find unusual observations (85 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Best way to find unusual observations (74 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (151 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Brain freeze: informat to read text "December 31, 2007"Brain freeze: informat to read text "December 31, 2007" (17 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Brain freeze: informat to read text "December 31, 2007" (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Brain freeze: informat to read text "December 31, 2007" (28 lines) From: Dave Scocca <dave@SCOCCA.ORG> Re: Brain freeze: informat to read text "December 31, 2007" (31 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Business ShopBusiness Shop (106 lines) From: Goteborgbank <cwmbanker@GMAIL.COM> Can I create a SAS program that prompts the user for input?Can I create a SAS program that prompts the user for input? (18 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: Can I create a SAS program that prompts the user for input? (44 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Best way to find unusual observationsBest way to find unusual observations (34 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (59 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (46 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (59 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (64 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Best way to find unusual observations (64 lines) From: data _null_, <datanull@GMAIL.COM> Re: Best way to find unusual observations (99 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Best way to find unusual observations (85 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Best way to find unusual observations (74 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Best way to find unusual observations (151 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Brain freeze: informat to read text "December 31, 2007"Brain freeze: informat to read text "December 31, 2007" (17 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Brain freeze: informat to read text "December 31, 2007" (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Brain freeze: informat to read text "December 31, 2007" (28 lines) From: Dave Scocca <dave@SCOCCA.ORG> Re: Brain freeze: informat to read text "December 31, 2007" (31 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Business ShopBusiness Shop (106 lines) From: Goteborgbank <cwmbanker@GMAIL.COM> Can I create a SAS program that prompts the user for input?Can I create a SAS program that prompts the user for input? (18 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: Can I create a SAS program that prompts the user for input? (44 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Brain freeze: informat to read text "December 31, 2007"Brain freeze: informat to read text "December 31, 2007" (17 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Brain freeze: informat to read text "December 31, 2007" (25 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Brain freeze: informat to read text "December 31, 2007" (28 lines) From: Dave Scocca <dave@SCOCCA.ORG> Re: Brain freeze: informat to read text "December 31, 2007" (31 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Business ShopBusiness Shop (106 lines) From: Goteborgbank <cwmbanker@GMAIL.COM> Can I create a SAS program that prompts the user for input?Can I create a SAS program that prompts the user for input? (18 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: Can I create a SAS program that prompts the user for input? (44 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Business ShopBusiness Shop (106 lines) From: Goteborgbank <cwmbanker@GMAIL.COM> Can I create a SAS program that prompts the user for input?Can I create a SAS program that prompts the user for input? (18 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: Can I create a SAS program that prompts the user for input? (44 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Can I create a SAS program that prompts the user for input?Can I create a SAS program that prompts the user for input? (18 lines) From: George Joseph <gjman@HOTMAIL.COM> Re: Can I create a SAS program that prompts the user for input? (44 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Comparing models :ModifiedComparing models :Modified (28 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Comparing models with negative BIC , AIC and maximum likelihoodComparing models with negative BIC , AIC and maximum likelihood (27 lines) From: Kwame Asom <asom77@HOTMAIL.COM> Re: Comparing models with negative BIC , AIC and maximum likelihood (43 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Computer Security Information and What You Can Do To Keep Your System Safe!Computer Security Information and What You Can Do To Keep Your System Safe! (275 lines) From: Andre.Lee.group.com@GMAIL.COM Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Confidence Limits around a percentileConfidence Limits around a percentile (27 lines) From: DJENSE00@YAHOO.COM <DJENSE00@YAHOO.COM> Re: Confidence Limits around a percentile (33 lines) From: data _null_, <datanull@GMAIL.COM> Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Consulting HelpConsulting Help (20 lines) From: William Elliott <elliott.willie@SBCGLOBAL.NET> Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Contract SAS and Stat positions in PA areaRe: Contract SAS and Stat positions in PA area (31 lines) From: Wu Consulting <wuconsulting2@HOTMAIL.COM> Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Convert a particular variables length in whole Library.Convert a particular variables length in whole Library. (33 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Convert a particular variables length in whole Library. (74 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Convert a particular variables length in whole Library. (106 lines) From: Jake Bee <johbee@GMAIL.COM> Re: Convert a particular variables length in whole Library. (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Couple of Proc Tabulate questionsCouple of Proc Tabulate questions (26 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (60 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (8 lines) From: wcw2 <wcw2@CDC.GOV> Re: Couple of Proc Tabulate questions (34 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Couple of Proc Tabulate questions (9 lines) From: wcw2 <wcw2@CDC.GOV> Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Create table names in Proc SQLCreate table names in Proc SQL (28 lines) From: yogi <yogibad@GMAIL.COM> Re: Create table names in Proc SQL (43 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Create table names in Proc SQL (55 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Crosstab HelpCrosstab Help (371 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Crosstab Help (396 lines) From: Vivek Kurup <vivekkr@FADMAIL.COM> Re: Crosstab Help (88 lines) From: Bob_Abelson@HGSI.COM Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Date Time IssuesDate Time Issues (20 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Re: Date Time Issues (32 lines) From: sonik son <sonikson@GMAIL.COM> Re: Date Time Issues (19 lines) From: Bill McKirgan <Bill.McKirgan@GMAIL.COM> Re: Date Time Issues (57 lines) From: Nordlund, Dan (DSHS/RDA) <NordlDJ@DSHS.WA.GOV> Re: Date Time Issues (128 lines) From: Reeza <fkhurshed@HOTMAIL.COM> Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Dependent variable in logistic regressionRe: Dependent variable in logistic regression (27 lines) From: Raven <rahul.dodhia@GMAIL.COM> Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Directing SAS Output to SharePoint Shared Documents locationDirecting SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (56 lines) From: Phil Rack <philrack@MINEQUEST.COM> Re: Directing SAS Output to SharePoint Shared Documents location (39 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (42 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (31 lines) From: JH <jenharper52@GMAIL.COM> Re: Directing SAS Output to SharePoint Shared Documents location (57 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Directing SAS Output to SharePoint Shared Documents location (76 lines) From: Alan Churchill <savian001@GMAIL.COM> Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Doubt about my DatasetDoubt about my Dataset (68 lines) From: surendar <surendar.gopal@GMAIL.COM> Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Duplicate recordsDuplicate records (53 lines) From: Anil Anand <anilkranand@GMAIL.COM> Re: Duplicate records (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Duplicate records (75 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Duplicate records (94 lines) From: jingtailan@gmail.com <jingtailan@GMAIL.COM> Re: Duplicate records (73 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Duplicate records (129 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
End of string bug in regular expression?Re: End of string bug in regular expression? (151 lines) From: Alex <internalsu@HOTMAIL.COM> Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Enterprise Miner data Help neededEnterprise Miner data Help needed (18 lines) From: cherub <cherub2life@YAHOO.COM> FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
FTP Compressed SAS Transport Files in WindowsFTP Compressed SAS Transport Files in Windows (30 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (48 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (70 lines) From: Steve James <spjcdc@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: data _null_, <datanull@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (113 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (134 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: FTP Compressed SAS Transport Files in Windows (81 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
FW: how to code cluster efficiently in SASFW: how to code cluster efficiently in SAS (63 lines) From: Jenny Zhang <jenny.zhang@UQ.EDU.AU> Re: FW: how to code cluster efficiently in SAS (83 lines) From: Andrew Hill <hill.andrewd@GMAIL.COM> FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
FW: wanna see catalog fileFW: wanna see catalog file (91 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Filename & pipe methodFilename & pipe method (67 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Re: Filename & pipe method (80 lines) From: Ken Barz <Ken.Barz@CPCMED.ORG> Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Firefox and ActiveX graph display problemFirefox and ActiveX graph display problem (28 lines) From: O'Connell, Martin <MOConnell@GEICO.COM> Re: Firefox and ActiveX graph display problem (29 lines) From: Jerry Davis <jwd@UGA.EDU> Re: Firefox and ActiveX graph display problem (32 lines) From: Graham Murray <graham.murray@WEBMINER.CO.UK> Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Floating Point RepresentationFloating Point Representation (63 lines) From: SAS Student <o.ibrahim0@GMAIL.COM> Re: Floating Point Representation (69 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: Floating Point Representation (100 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: Floating Point Representation (86 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13Free Online: Data Mining Intro for Beginners, Vendor-Neutral, December 13 (40 lines) From: Lisa Solomon <lisas@SALFORD-SYSTEMS.COM> Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Fw: macro var questionFw: macro var question (39 lines) From: Masuod Pajoh <mpajoh@ODOT.ORG> GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
GEE and within subject variationGEE and within subject variation (20 lines) From: duo wan <duo_wan@YAHOO.COM> GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
GLIMMIX covtest?GLIMMIX covtest? (18 lines) From: Nicki Bush <enbush@GMAIL.COM> Re: GLIMMIX covtest? (30 lines) From: Oliver.Kuss@MEDIZIN.UNI-HALLE.DE Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Get observation in a variable column nameGet observation in a variable column name (27 lines) From: Fernando Tenorio <fetcs74@GMAIL.COM> Re: Get observation in a variable column name (61 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (51 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Get observation in a variable column name (64 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Get observation in a variable column name (85 lines) From: data _null_, <datanull@GMAIL.COM> Re: Get observation in a variable column name (90 lines) From: fernandoedouardo.tenorio@FORTIS.COM Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Getting Page x of y using line statementGetting Page x of y using line statement (84 lines) From: SAS_learner <proccontents@GMAIL.COM> Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Getting macro variable to work in proc exportGetting macro variable to work in proc export (599 lines) From: Kevin F. Spratt <Kevin.F.Spratt@DARTMOUTH.EDU> Re: Getting macro variable to work in proc export (623 lines) From: toby dunn <tobydunn@HOTMAIL.COM> HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
HELP!! Can this be done in SAS??Re: HELP!! Can this be done in SAS?? (147 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: HELP!! Can this be done in SAS?? (13 lines) From: Sas Learner <sas.learner@LIVE.COM.AU> HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
HELP!! How can I make SAS do this??Re: HELP!! How can I make SAS do this?? (123 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Help! SAS NLMIXED. The final Hessian matrix is not positiveRe: Help! SAS NLMIXED. The final Hessian matrix is not positive (106 lines) From: sphuang via MathKB.com <u39394@UWE.UGA.EDU> How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
How do I stop "proc report" from throwing an unwanted line?How do I stop "proc report" from throwing an unwanted line? (95 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (136 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How do I stop "proc report" from throwing an unwanted line? (162 lines) From: RolandRB <rolandberry@HOTMAIL.COM> How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
How does SAS calculate percentiles.How does SAS calculate percentiles. (17 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (43 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: How does SAS calculate percentiles. (49 lines) From: souga soga <souga1234@GMAIL.COM> Re: How does SAS calculate percentiles. (32 lines) From: Warren Schlechte <Warren.Schlechte@TPWD.STATE.TX.US> Re: How does SAS calculate percentiles. (44 lines) From: souga soga <souga1234@GMAIL.COM> How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
How to address .XPT file in Proc sqlHow to address .XPT file in Proc sql (22 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (66 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (98 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (39 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (51 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to address .XPT file in Proc sql (133 lines) From: Ed Heaton <EdHeaton@WESTAT.COM> Re: How to address .XPT file in Proc sql (10 lines) From: SUBSCRIBE SAS-L Dan <deniseyu001@GMAIL.COM> Re: How to address .XPT file in Proc sql (84 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to address .XPT file in Proc sql (116 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
How to be helpful, how to get helpHow to be helpful, how to get help (38 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: How to be helpful, how to get help (58 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: How to be helpful, how to get help (22 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Re: How to be helpful, how to get help (11 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
How to compile a bunch of macrosHow to compile a bunch of macros (22 lines) From: Sam <sas.zheng@GMAIL.COM> Re: How to compile a bunch of macros (50 lines) From: Ya Huang <ya.huang@AMYLIN.COM> How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
How to import data which has more than 20,000 variables.ThanksHow to import data which has more than 20,000 variables.Thanks (23 lines) From: cherub <cherub2life@YAHOO.COM> Re: How to import data which has more than 20,000 variables.Thanks (37 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to import data which has more than 20,000 variables.Thanks (83 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (135 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (145 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (159 lines) From: Peter <crawfordsoftware@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (53 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (76 lines) From: data _null_, <datanull@GMAIL.COM> Re: How to import data which has more than 20,000 variables.Thanks (118 lines) From: Peter <crawfordsoftware@GMAIL.COM> How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
How to load compiled macro into memoryHow to load compiled macro into memory (21 lines) From: Haishan Zheng <sas.zheng@GMAIL.COM> Re: How to load compiled macro into memory (43 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
How to strip down the web dataHow to strip down the web data (19 lines) From: stephillup@YAHOO.COM Re: How to strip down the web data (32 lines) From: Scott Barry <sbarry@SBBWORKS.COM> Re: How to strip down the web data (31 lines) From: Lex Jansen <lexjansen@GMAIL.COM> Re: How to strip down the web data (65 lines) From: Gerry <gpauline@PACE.EDU> Re: How to strip down the web data (29 lines) From: xav <xav29atao@YAHOO.FR> IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
IF vs WHERE discussionIF vs WHERE discussion (25 lines) From: LWn <Lars.WahlgrenRemove@THIS.STAT.LU.SE> Re: IF vs WHERE discussion (32 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (66 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (43 lines) From: Perry <jasper6294@GMAIL.COM> Re: IF vs WHERE discussion (86 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (48 lines) From: Pardee, Roy <pardee.r@GHC.ORG> Re: IF vs WHERE discussion (78 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (131 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (59 lines) From: Carol Bristow <Carol.Bristow@DPRA.COM> Re: IF vs WHERE discussion (139 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (144 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (253 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: IF vs WHERE discussion (155 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (149 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (163 lines) From: bruce johnson <chimanbj@GMAIL.COM> Re: IF vs WHERE discussion (169 lines) From: data _null_, <datanull@GMAIL.COM> Re: IF vs WHERE discussion (16 lines) From: tanwan <tanwanzang@YAHOO.COM> Re: IF vs WHERE discussion (168 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: IF vs WHERE discussion (71 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Interpretation of a macro variableInterpretation of a macro variable (27 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Interpretation of a macro variable (78 lines) From: Jack Clark <JClark@CHPDM.UMBC.EDU> Re: Interpretation of a macro variable (29 lines) From: Patrick <patrick.matter@GMX.CH> Re: Interpretation of a macro variable (49 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Is SAS supported on a virtual server?Is SAS supported on a virtual server? (12 lines) From: Andy Andrews <sas_andy@BOOSECAT.COM> Re: Is SAS supported on a virtual server? (34 lines) From: Alan Churchill <savian001@GMAIL.COM> Re: Is SAS supported on a virtual server? (56 lines) From: Dave Hogg <D.Hogg@CURTIN.EDU.AU> Re: Is SAS supported on a virtual server? (16 lines) From: Patrick <patrick.matter@GMX.CH> LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
LIBNAME XML and "binary" char dataLIBNAME XML and "binary" char data (80 lines) From: droide <barnet@NC.RR.COM> LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
LINQ, anyone?LINQ, anyone? (18 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
LL3 distribution fittingRe: LL3 distribution fitting (57 lines) From: Ping <psw205@GMAIL.COM> Re: LL3 distribution fitting (92 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: LL3 distribution fitting (94 lines) From: Ping <psw205@GMAIL.COM> Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Large amount of data in Proc NLPLarge amount of data in Proc NLP (21 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (53 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large amount of data in Proc NLP (15 lines) From: Ricardo de Oliveira Lopes Junior <ricardo.lopes@ITAU.COM.BR> Re: Large amount of data in Proc NLP (45 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Learning to program better and in a more organized wayRe: Learning to program better and in a more organized way (76 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Re: Learning to program better and in a more organized way (42 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Re: Learning to program better and in a more organized way (66 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: Learning to program better and in a more organized way (100 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Learning to program better and in a more organized way (127 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (98 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (64 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Learning to program better and in a more organized way (137 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Learning to program better and in a more organized way (116 lines) From: Paul A. Thompson <paul@WUBIOS.WUSTL.EDU> Re: Learning to program better and in a more organized way (119 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Learning to program better and in a more organized way (274 lines) From: Mary <mlhoward@AVALON.NET> Re: Learning to program better and in a more organized way (240 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Length of variable namesLength of variable names (37 lines) From: Raven <rahul.dodhia@GMAIL.COM> Re: Length of variable names (44 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Length of variable names (56 lines) From: Ian Whitlock <iw1junk@COMCAST.NET> Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Logistic regression AIC and C-valueLogistic regression AIC and C-value (14 lines) From: Little T <xiao.chacha@GMAIL.COM> Re: Logistic regression AIC and C-value (32 lines) From: Wensui Liu <liuwensui@GMAIL.COM> Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Macro variable in proc formatMacro variable in proc format (27 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (50 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Macro variable in proc format (38 lines) From: sas biology <sasbio@GMAIL.COM> Re: Macro variable in proc format (70 lines) From: data _null_, <datanull@GMAIL.COM> Macro variable in proc format (23 lines) From: Jay Jacob Wind <jay.wind@ATT.NET> Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Meta-Analysis LiteratureRe: Meta-Analysis Literature (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (73 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Meta-Analysis Literature (69 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Meta-Analysis Literature (384 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Multivariate timeseries regression questionMultivariate timeseries regression question (19 lines) From: Raghu Venkat <raghustays@GMAIL.COM> NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
NLP save output to fileNLP save output to file (22 lines) From: john.tseven@GMAIL.COM Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Negative values in macro variable listNegative values in macro variable list (45 lines) From: clareaihw <clare.lahiff@AIHW.GOV.AU> Re: Negative values in macro variable list (54 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Negative values in macro variable list (85 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Negative values in macro variable list (90 lines) From: Howard Schreier <hs AT dc-sug DOT org> <nospam@HOWLES.COM> Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Normality CodeNormality Code (51 lines) From: June <jgothberg@YAHOO.COM> Re: Normality Code (72 lines) From: Ian Wakeling <ian.wakeling@HANANI.QISTATS.CO.UK> Re: Normality Code (7 lines) From: June Gothberg <jgothberg@YAHOO.COM> OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
OT: Chance to Make SAS-L History: Did You Know That...Re: OT: Chance to Make SAS-L History: Did You Know That... (101 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: OT: Chance to Make SAS-L History: Did You Know That... (109 lines) From: data _null_, <datanull@GMAIL.COM> OT: Chance to Make SAS-L History: Did You Know That... (62 lines) From: Nat Wooding <Nathaniel.Wooding@DOM.COM> OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
OT: Friday HumorOT: Friday Humor (61 lines) From: Fehd, Ronald J. (CDC/CCHIS/NCPHI) <rjf2@CDC.GOV> OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
OT: Friday humor (was: Very Urgent ... Need Programmer)OT: Friday humor (was: Very Urgent ... Need Programmer) (204 lines) From: Gregg Snell <sas-l@DATASAVANTCONSULTING.COM> Re: OT: Friday humor (was: Very Urgent ... Need Programmer) (235 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
OT: Gmail invitesOT: Gmail invites (16 lines) From: AnnHett <annhett@GMAIL.COM> Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Odd SAS question about HardwareOdd SAS question about Hardware (24 lines) From: Bliskner@GMAIL.COM Re: Odd SAS question about Hardware (39 lines) From: Alan Churchill <savian001@GMAIL.COM> Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Options MFILE MPRINT - outputs code different than code initially runOptions MFILE MPRINT - outputs code different than code initially run (66 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Re: Options MFILE MPRINT - outputs code different than code initially run (74 lines) From: data _null_, <datanull@GMAIL.COM> Re: Options MFILE MPRINT - outputs code different than code initially run (33 lines) From: Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Ordered logit/probitOrdered logit/probit (18 lines) From: Kitty Lee <lee.kitty@YAHOO.COM> Re: Ordered logit/probit (38 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Ordered logit/probit (36 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
PROC MixedPROC Mixed (12 lines) From: Dinesh Sharma <dinesh.sharma@FIU.EDU> Re: PROC Mixed (27 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
PROC NLIN - non-fixed number of PARMSPROC NLIN - non-fixed number of PARMS (17 lines) From: Jesper Sahner Pedersen <jespersahner@HOTMAIL.COM> Re: PROC NLIN - non-fixed number of PARMS (54 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
PROC ODBC ( importing XLS )PROC ODBC ( importing XLS ) (34 lines) From: Aj <ajeetsubramanian@GMAIL.COM> Re: PROC ODBC ( importing XLS ) (45 lines) From: Don <dmorgan@ROCKETMAIL.COM> Re: PROC ODBC ( importing XLS ) (48 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: PROC ODBC ( importing XLS ) (56 lines) From: Audimar P. Bangi <audi@SAS2THEMAX.COM> Re: PROC ODBC ( importing XLS ) (62 lines) From: Workman, Rob <Rob.Workman@SORIN.COM> Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Pharms Reporting is moving away from the ASCII format ?Pharms Reporting is moving away from the ASCII format ? (25 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (27 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (30 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (83 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (92 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (115 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: Pharms Reporting is moving away from the ASCII format ? (159 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (95 lines) From: Lou <lpogodajr292185@COMCAST.NET> Re: Pharms Reporting is moving away from the ASCII format ? (158 lines) From: cyew07@YAHOO.CO.UK Re: Pharms Reporting is moving away from the ASCII format ? (167 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Pivoting survey responses into binary variables - when, why ?
Pivoting survey responses into binary variables - when, why ?